spec-tasks

Files (1)

• SKILL.md

SKILL.md (first lines)

# Spec Tasks

Use this skill to turn accepted requirements and design into an implementation plan.

## Required Reads

Before editing tasks, read:

- `.specs/<feature>/brainstorm.md`
- `.specs/<feature>/requirements.md`
- `.specs/<feature>/design.md`
- Existing `.specs/<feature>/tasks.md`, if present

## Output File

Write tasks to:

```text
.specs/<feature-slug>/tasks.md
```

Start from `../../templates/spec/tasks.md` when creating a new task list.

## Task Quality Bar

Each implementation task should be:

- Small enough for one focused coding pass
- Ordered to reduce rework and expose risk early
- Written as a checkbox (`- [ ]`)
- Mapped to requirement IDs
- Annotated with likely files/areas
- Given a validation command or manual check

Prefer this shape:

```markdown
- [ ] 1. Implement TODO
  - Requirement(s): FR-001, NFR-001
  - Files/areas: src/...
  - Validation: pnpm test ...
```

## Sequencing Guidance

Typical order:

1. Foundation/schema/config changes
2. Core behavior
3. Integration points
4. Error handling and edge cases
5. Tests
6. Docs/migration/cleanup

## Approval Gate

- Only start tasks when `design.md` is `Status: design-approved`. If it is still `design-draft`, stop and ask the user to approve the design first.
- Keep `tasks.md` at `Status: tasks-draft` while awaiting review.
- After drafting tasks, stop and ask the user to explicitly approve the task plan. Do **not** start implementation in the same turn.
- When the user explicitly approves the task plan, update the `Status:` line in `tasks.md` to `tasks-approved`, then run `spec_validate` with `phase: "implementation"`. Only then may implementation begin.

## Done Criteria

Before asking for implementation approval:

- `Status: tasks-draft` remains in place while the plan is under review
- Every requirement appears in at least one task
- Every task has a validation path
- Design testing strategy is represented by tasks
- Risky migrations or rollouts have explicit tasks

Implementation may start only after explicit user approval updates the status to `tasks-approved` and implementation-readiness validation passes.

From ovitinhooo/pi-spec, MIT.

More from ovitinhooo/pi-spec