/cardume-core:tasks — Plan the work
$ARGUMENTS
Who writes tasks.md. At level 2, whoever runs this skill (usually the main session). At level 3,
software-architect writes it for each feature once that feature's spec is approved, using these
rules and the contracts in docs/prd/<slug>-architecture.md. The input is always a spec: a PRD is
never broken into tasks directly — each feature in it gets a spec first (spec skill; its quick spec
when speed matters).
- Read the spec. If no path was given, use the most recently modified
docs/specs/*/spec.md.
If its status is not approved, show the open questions and stop — tasks built on an
unapproved spec get redone. (Quick spec, see the spec skill: spec and tasks are written in one
pass and approved together.) If you were given a PRD, stop and name the features that need a spec.
- Read the files listed in the spec's Design section to ground the breakdown in the real code.
- Write
docs/specs/<slug>/tasks.md:
# Tasks — <Feature name>
Spec: ./spec.md
Status: draft | approved
- [ ] T1 — <imperative title>
- Requirements: R1, R3
- Lane / agent: backend / backend-specialist
- Contracts: <types/schema/fixture this task uses or defines>
- Files: src/..., tests/...
- Steps: <2–5 short concrete steps, each naming the exact file it touches>
- Verify: `<command that proves it>` (test name, curl, script) + expected result
- Depends on: —
- Issue: #<n> (only with --issues)
Breakdown rules
- Small. A task is one focused commit a fresh subagent can finish and verify in one session,
written as short concrete steps with exact file paths. Split anything that touches unrelated areas.
- Contracts first. When tasks in different lanes (backend, frontend, data, infra) meet, add an
early task that defines the contract between them (types, API/JSON schema, event format) and a
fixture with sample data. Later tasks depend on the contract, never on "wait for the other task",
so lanes can run in parallel. At level 3, reuse the contracts already defined in the architecture file.
- Owner lane per task (
Lane: backend | frontend | data | infra | content | qa) next to the agent.
- Test first where it fits. For logic, the first task (or first step of a task) adds a failing
test for the requirement; the implementation makes it pass.
- Properties get a task. Each filled Property cell in the spec gets a task (or a step) that
writes a property-based test with the project's library (fast-check, Hypothesis, jqwik, proptest);
its
Verify runs that test.
- Every requirement is covered. End the file with a coverage table
R-ID → tasks (mark property
tests, e.g. R2 → T3, T5 (property)); a requirement with no task is a gap to fix now.
- Order by dependency, then by risk (riskiest first, so surprises come early).
- Agent is the Cardume agent best suited (see
intelligent-routing); use general-purpose
when none fits.
- Verify must be executable — never "check it works".
- Decisions made while breaking down (technology, pattern, trade-off) go into an ADR via the
adr skill.
Analyze before approval
Read spec.md and tasks.md side by side once and fix what fails, because gaps found here cost minutes
and gaps found during implement cost a redo:
- Every requirement (R-ID) and every property is covered by at least one task.
- No task lacks a requirement — work without one is scope creep or a missing requirement; add the
requirement to the spec (and tell the user) or drop the task.
- Every contract is defined by an earlier task than the first task that uses it.
- No unresolved
[NEEDS CLARIFICATION] remains in the spec.
- Show the user the task list, the coverage table and the analyze result, and ask for approval (or,
as a subagent, return them under Open questions for the caller to get it). When approved, set
Status: approved. Next step: /cardume-core:implement docs/specs/<slug>/tasks.md.
Optional: --issues (GitHub issues)
Only when --issues was passed or the user asks for it — never by default, because creating issues
is visible to other people. After tasks.md is approved:
- Check
gh auth status and that the repo has a GitHub remote; if not, say so and stop.
- Prepare one
gh issue create command per unchecked task: --title "<slug> T<n>: <title>",
--body with the requirement IDs, the Verify command, the dependencies and a link back to
docs/specs/<slug>/tasks.md, and --label for the lane (only labels that exist — check with
gh label list).
- Show the commands and ask the user to confirm (as a subagent, return them under Open
questions and stop). Run them only after a yes.
- Write each issue number back into its task (
- Issue: #<n>), so tasks.md stays the source of truth.
1---2name: tasks3description: "Breaks an approved spec into ordered tasks in tasks.md, each with an owner and a verification command, optionally opening GitHub issues. Use after a spec is approved, before implementing level-2/3 work."4argument-hint: "[path to spec.md] [--issues]"5compatibility: "Claude Code with the Cardume plugins (uses cardume-* commands, subagents or plugin paths); the guidance itself is portable."6metadata:7 source: https://skillmd.com/skills/jeffersonvalente/tasks8---910# /cardume-core:tasks — Plan the work1112$ARGUMENTS1314**Who writes tasks.md.** At level 2, whoever runs this skill (usually the main session). At level 3,15`software-architect` writes it for each feature once that feature's spec is approved, using these16rules and the contracts in `docs/prd/<slug>-architecture.md`. The input is always a spec: a PRD is17never broken into tasks directly — each feature in it gets a spec first (`spec` skill; its quick spec18when speed matters).19201. Read the spec. If no path was given, use the most recently modified `docs/specs/*/spec.md`.21 If its status is not `approved`, show the open questions and stop — tasks built on an22 unapproved spec get redone. (Quick spec, see the `spec` skill: spec and tasks are written in one23 pass and approved together.) If you were given a PRD, stop and name the features that need a spec.242. Read the files listed in the spec's Design section to ground the breakdown in the real code.253. Write `docs/specs/<slug>/tasks.md`:2627```markdown28# Tasks — <Feature name>2930Spec: ./spec.md31Status: draft | approved3233- [ ] T1 — <imperative title>34 - Requirements: R1, R335 - Lane / agent: backend / backend-specialist36 - Contracts: <types/schema/fixture this task uses or defines>37 - Files: src/..., tests/...38 - Steps: <2–5 short concrete steps, each naming the exact file it touches>39 - Verify: `<command that proves it>` (test name, curl, script) + expected result40 - Depends on: —41 - Issue: #<n> (only with --issues)42```4344## Breakdown rules4546- **Small.** A task is one focused commit a fresh subagent can finish and verify in one session,47 written as short concrete steps with exact file paths. Split anything that touches unrelated areas.48- **Contracts first.** When tasks in different lanes (backend, frontend, data, infra) meet, add an49 early task that defines the contract between them (types, API/JSON schema, event format) and a50 fixture with sample data. Later tasks depend on the contract, never on "wait for the other task",51 so lanes can run in parallel. At level 3, reuse the contracts already defined in the architecture file.52- **Owner lane** per task (`Lane: backend | frontend | data | infra | content | qa`) next to the agent.53- **Test first where it fits.** For logic, the first task (or first step of a task) adds a failing54 test for the requirement; the implementation makes it pass.55- **Properties get a task.** Each filled **Property** cell in the spec gets a task (or a step) that56 writes a property-based test with the project's library (fast-check, Hypothesis, jqwik, proptest);57 its `Verify` runs that test.58- **Every requirement is covered.** End the file with a coverage table `R-ID → tasks` (mark property59 tests, e.g. `R2 → T3, T5 (property)`); a requirement with no task is a gap to fix now.60- **Order by dependency**, then by risk (riskiest first, so surprises come early).61- **Agent** is the Cardume agent best suited (see `intelligent-routing`); use `general-purpose`62 when none fits.63- **Verify** must be executable — never "check it works".64- **Decisions** made while breaking down (technology, pattern, trade-off) go into an ADR via the `adr` skill.6566## Analyze before approval6768Read spec.md and tasks.md side by side once and fix what fails, because gaps found here cost minutes69and gaps found during implement cost a redo:7071- Every requirement (R-ID) and every property is covered by at least one task.72- No task lacks a requirement — work without one is scope creep or a missing requirement; add the73 requirement to the spec (and tell the user) or drop the task.74- Every contract is defined by an earlier task than the first task that uses it.75- No unresolved `[NEEDS CLARIFICATION]` remains in the spec.76774. Show the user the task list, the coverage table and the analyze result, and ask for approval (or,78 as a subagent, return them under **Open questions** for the caller to get it). When approved, set79 `Status: approved`. Next step: `/cardume-core:implement docs/specs/<slug>/tasks.md`.8081## Optional: `--issues` (GitHub issues)8283Only when `--issues` was passed or the user asks for it — never by default, because creating issues84is visible to other people. After tasks.md is approved:85861. Check `gh auth status` and that the repo has a GitHub remote; if not, say so and stop.872. Prepare one `gh issue create` command per unchecked task: `--title "<slug> T<n>: <title>"`,88 `--body` with the requirement IDs, the Verify command, the dependencies and a link back to89 `docs/specs/<slug>/tasks.md`, and `--label` for the lane (only labels that exist — check with90 `gh label list`).913. Show the commands and ask the user to confirm (as a subagent, return them under **Open92 questions** and stop). Run them only after a yes.934. Write each issue number back into its task (`- Issue: #<n>`), so tasks.md stays the source of truth.