Loading...
Loading...
Found 84 Skills
Standard workflow for implementing features with specs and planning documents. Use when starting a new feature, planning implementation, or working on any non-trivial task.
Auto-generate project workflow config (docs/workflow.md) from existing PRD and CLAUDE.md with zero questions. Use when user says "set up workflow", "configure TDD", "wire up dev workflow", or after running /scaffold before /plan. Do NOT use for founder setup (use /init) or project scaffolding (use /scaffold).
Issue Workflow Stage 3——Fix code precisely based on confirmed root cause and solution, verify the effect, and document it in {slug}-fix-note.md. This is the final stage of the issue workflow—no verification loop means the workflow is incomplete. Two entry points: the standard path is triggered from easysdd-issue-analyze (with existing {slug}-analysis.md), and the quick path is triggered directly from easysdd-issue-report (without {slug}-analysis.md, as the root cause was determined by AI reading code during the report stage). Trigger scenarios: user says 'Start fixing the bug', 'Fix according to analysis', 'Start modifying code'. During repair, only modify the files stated in the solution; do not optimize casually or introduce new abstractions—these actions will make the scope spread to untraceable levels.
Brownian Ratchet progress gates for RPI workflow. Check, record, verify. Triggers: "check gate", "verify progress", "ratchet status".
Manage .flow/ tasks and epics. Triggers: 'show me my tasks', 'list epics', 'what tasks are there', 'add a task', 'create task', 'what's ready', 'task status', 'show fn-1-add-oauth'. NOT for /flow-next:plan or /flow-next:work.
Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"
Split plans, specs, or current conversations into a set of tracer-bullet tickets, each declaring blocking edges, and publish them to the configured tracker; use text edges in per-ticket files locally, and native blocking links in real trackers.
Clarify requirements before implementing. Use when serious doubts arise.
Manages deferred/blocked work items as GitHub Issues with labels and blocker tracking
Linear ticket lifecycle for any project. Use when starting work on a Linear issue, ending work on an issue, or asking what to work on next. Triggers: start KAT-N, pick up, implement, finish, complete, done with, close, what's next, next ticket, next issue. Handles blocker validation, status transitions, context loading, branch creation, evidence gating, and chain promotion.
Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.
Cancel and permanently delete an in-progress spec-driven change. Warns before deleting. Use this to abandon a change that will not be implemented.