breakdown

"This skill should be used when the user needs to derive a batch of task files from existing usecase / spec / architecture inputs. Common triggers include: 'breakdown', 'derive tasks', 'task batch', 'batch tasks from spec', 'plan the implementation tasks'. Writes per-task files at a4/task/<id>-<slug>.md only — no wiki page output. Requires (usecase OR spec) AND ci.md to enter; otherwise redirects to /a4:ci-setup, /a4:spec, /a4:usecase, or /a4:task. The agent-driven implement + test loop is in /a4:auto-coding; single ad-hoc tasks come through /a4:task, /a4:bug, /a4:spike, /a4:research."

Safety Notice

This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.

Copy this and send it to your AI assistant to learn

Install skill "breakdown" with this command: npx skills add studykit/skillsmp-studykit-studykit-breakdown

No markdown body

This source entry does not include full markdown content beyond metadata.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHub

Related Skills

Related by shared tags or category signals.

Research

discard

This skill should be used when the user wants to discard an existing task across any of the four issue families (task / bug / spike / research). Common triggers: 'discard task <id>', 'drop task <id>', 'abandon this task', 'task <id> is no longer needed'. The skill flips the task's `status:` to `discarded` via direct frontmatter edit (the PostToolUse cascade hook refreshes `updated:`) and optionally appends a `## Why Discarded` body note. UC-cascade discards (when a UC flips to `discarded` and the cascade hook auto-discards related tasks) are not in scope — they are handled by the hook automatically. Authoring is the matching `/a4:task`, `/a4:bug`, `/a4:spike`, or `/a4:research` skill.

Repository SourceNeeds Review

-0studykit

Research

bug

This skill should be used when the user wants to log a single bug task — a tracked defect fix against expected behavior. Common triggers: 'log a bug', 'create a bug task', 'open a bug for X', 'track this regression', 'file a bug'. Optional implements: (UC paths the bug traces to) and/or spec: (spec paths whose expected behavior the bug violates); writes a4/bug/<id>-<slug>.md. Single-task entry. For batch UC/spec-driven generation use /a4:breakdown; for the implement loop use /a4:auto-coding; for task/spike/research use the matching skill (/a4:task, /a4:spike, /a4:research); to discard a task use /a4:discard.

Repository SourceNeeds Review

-0studykit

Research

task

This skill should be used when the user wants to author a task — a unit of regular implementation work (new functionality, extension, refactor). Common triggers: 'add a task', 'create a task', 'I need a task for', 'task for <UC>'. Optional implements: (UC paths) and/or spec: (spec paths); writes a4/task/<id>-<slug>.md. For bug/spike/research use the matching skill (/a4:bug, /a4:spike, /a4:research); to discard a task use /a4:discard.

Repository SourceNeeds Review

-0studykit

General

arch

"This skill should be used when the user needs to design or iterate on system architecture — technology stack, external dependencies, component design, information flows, interface contracts, and test strategy. Common triggers include: 'architecture', 'design the system', 'component design', 'tech stack', 'how should we build this', 'system design', 'interface contracts', 'test strategy', 'what tools should we use'. Writes the result as a4/architecture.md (wiki page) following the spec-as-wiki+issues layout."

Repository SourceNeeds Review

-0studykit