.Cursor

Epic lifecycle orchestrator. Invoke only via /epic.

Story lifecycle orchestrator. Invoke only via /story.

Re-engineers validated work after deliberate change. Use after validation to rebuild and re-prove a redesign or pivot.

Hardens post-validation defects and missed gates. Use for bugs; use adjust for deliberate redesign.

Runs decorrelated planning analysis. Use after project-plan, epic-breakdown, or story-tasks before downstream work.

User-only router for /validate --level. Auto-selection uses the project, epic, or story validator directly.

Writes epic-tech-spec.md with design and traceability. Use after epic clarification and optional architecture work.

Defines project UX strategy. Use before project-plan for Platform or Build projects with four-plus epics.

Exercises real user or operator jobs. Use after audit before story, epic, or project validation.

Extracts code-side facts at project, epic, or story scope. Use for brownfield work or a fresh reality check.

Writes plan.md with design, contracts, and tests. Use after story clarification or code scan, before story-tasks.

Audits implemented work adversarially. Use after implementation and before any story or epic validation.

Captures a project learning at discovery. Use when waiting for retrospective risks losing or repeating it.

Writes executable tasks.md from the story plan. Use after story-plan and optional UI spec, before implementation.

Fills gaps in epic.md. Use after epic-specify when scope, boundaries, or technical intent are unclear.

Maps epic touchpoints, emotions, and flow. Use after epic-clarify and any architecture, before wireframes or epic-plan.

Retired alias → speck-skeptical-review / story-tasks. Use when /epic-outline named.

Creates epic.md from a project-plan placeholder or new scope. Use before epic-clarify and downstream epic work.

Creates PRD.md, epics, and E000. Use after required PROMISE artifacts and before any epic work.

Discovers epic boundaries from existing code and docs. Use before epic-specify when brownfield work has no epic map.

Validates an epic across completed stories and audit evidence. Use at the epic prove gate before retrospective.

Regenerates project-state.md from current truth. Use after truth-affecting gates land on main.

Upgrades Speck and repairs compatibility state. Use when an upgrade is requested or engagement finds a legacy marker.

Detects engagement drift. Use before project work in new or stale sessions, after ownership changes, or on recheck.

Reverse-engineers story specs and code scans. Use at story entry before story-clarify when code lacks Speck artifacts.

Creates story spec.md. Use after epic-breakdown or for new scope, before story-clarify and story-plan.

Creates ui-spec.md for complex UI. Use after story-plan before story-tasks for multi-state or interactive work.

Maps an epic to ordered, traceable stories. Use after epic-plan and before starting story work.

Models domain terms, rules, and invariants. Use after project-clarify before foundation work for specialized domains.

Extracts project context from existing docs. Use at brownfield start before speck-scan and project-specify.

Captures and deduplicates Speck methodology issues. Use when the process itself exposes a gap or defect.

Validates a story after audit and declares readiness. Use at the story prove gate before retrospective.

Applies project visual personality and quality rules. Use while building or reviewing user-facing UI components.

Produces host-specific visual and accessibility evidence. Use during UI LARP after the target build becomes reachable.

Creates screen-by-screen epic wireframes. Use for UX-heavy epics after epic-journey and before epic-plan.

Creates context.md for team, stack, compliance, and constraints. Use after project-clarify before project-plan.

Refreshes declared PROFILE surfaces. Use after product-contract changes before evidence-contract or when drift appears.

Sequences epics, dependencies, and resources. Use after project-plan for multi-team or multi-quarter Platform delivery.

Creates project.md vision and boundaries. Use when starting after any needed brainstorming or brownfield import.

Scores seeded defects against Speck gates. Use only in the Speck source repo before changing methodology gates.

Implements analyzed story work. Use after required spec, plan, tasks, and story analysis before speck-audit.

Validates project outcomes across completed epics. Use at the project prove gate before project retrospective.

Defines local epic principles. Use after epic-clarify before epic-architecture or epic-plan when local rules are needed.

Synthesizes story retros into epic-retro.md. Use after epic-validate when closing an epic.

Turns a vague idea into a structured problem. Use before project-specify when product intent is still fuzzy.

Appends a decision lock to the project log. Use at phase boundaries whenever a non-trivial choice is locked.

Scans current methodology or product frontiers. Use for SOTA research or live-market claim rechecks.

Captures story outcomes and learnings in story-retro.md. Use after story-validate when closing a story.

Designs project system architecture. Use before project-plan for Platform, cross-system, or four-plus-epic work.

Defines project technical principles. Use after project-context before project-architecture when governance is needed.

Defines epic UI seams and emotional flow. Use after any epic UX artifacts before epic-plan for user-facing epics.

Researches external facts. Use before locking choices about technology, standards, compliance, markets, or integrations.

Defines tokens, primitives, and component standards. Use after project-architecture before project-plan for shared UI.

Synthesizes epic retros into project-retro.md. Use after project-validate when closing a project phase.

Challenges the assumptions and value behind a commitment. Use before a high-impact lock or when evidence undermines it.

Creates product-contract.md for promises and differentiation. Use at Build/Platform before project-plan or epic work.

Defines product proof and readiness gates. Use at Build/Platform after product-contract and before project-plan.