Skip to main content
paulund

1 min read

#ai #spec-driven-development #templates

Task: [Feature Name]

Date: YYYY-MM-DD Status: Pending

Description

[Clear description of what needs to be built and why. Provide context about the problem this solves and the value it provides.]

Requirements

  1. [Specific, measurable requirement]
  2. [Another requirement]
  3. [Another requirement]

Acceptance Criteria

  • [Specific, testable criterion - what defines success?]
  • [Another criterion]
  • [Another criterion]

Additional Context

Technical Constraints (if any)

  • [Performance requirements, system limitations, etc.]

Dependencies (if any)

  • [External libraries, APIs, other features this depends on]

Edge Cases (if known)

  • [Unusual inputs or scenarios to handle]
  • [Error conditions to consider]

References (if applicable)

  • [Link to designs, mockups, or related docs]
  • [Related tickets or issues]

AI Planning Section

The AI will fill in this section after reviewing the spec above. To trigger planning, ask: "Read this spec and create an implementation plan following the project instructions."

Proposed Approach

Files to Create/Modify

Implementation Steps

Testing Strategy

Potential Challenges

Related notes

  • Tasks Directory

    Overview of the tasks directory structure for spec-driven development, including how to create, mana...

  • AI Job Interviews

    AI tools have broken traditional software engineering interviews. Here's how hiring practices need t...

  • AI Rules

    How to define rules and guidelines for AI coding tools like Claude Code and GitHub Copilot to ensure...


Newsletter

A weekly newsletter on backend architecture, AI-assisted development, and engineering. No spam, unsubscribe any time.