defining-stories
Guides creation of user stories and epic design documents. Use when defining new features, writing Given-When-Then criteria, creating story logs, or designing larger features that need scope definition.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Guides creation of user stories and epic design documents. Use when defining new features, writing Given-When-Then criteria, creating story logs, or designing larger features that need scope definition.
Permanently delete a background mission and all its run history. This action cannot be undone. Use when the user explicitly asks to delete or remove a mission. Always confirm with the user before deleting. Keywords: mission, delete, remove, cancel, destroy, permanently.
Ensure artifacts, validation, and rollout readiness for handoff.
Facilitate a cross-functional design review capturing decisions, feedback, and implementation guidance.
Map and visualize feature dependencies. Use when analyzing dependencies, identifying blockers, or creating dependency graphs. Triggers on keywords like "dependencies", "blockers", "what blocks", "dependency map".
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.
PROACTIVELY track and document project design decisions without being asked. Activate automatically when detecting architecture discussions, implementation decisions, pattern choices, library selections, or any technical decisions. Also use when user explicitly says "記録して", "設計どうなってる", "record this". Do NOT wait for user to ask - record important decisions immediately.
Cleanly stop an active engineering layer flow (dev-autopilot, dev-deep-interview, dev-plan) and report what was completed. Use when the user says "cancel", "stop", "abort", "cancelomc", or wants to exit a multi-phase dev workflow.
Multi-perspective consensus planning with Planner/Architect/Critic loop. Use when high-stakes decisions need RALPLAN-DR structured deliberation (auth, migrations, public APIs, irreversible changes). Pairs with @compass-planner + @apex-architect + @raven-critic.
Persist context across engineering sessions — save important decisions, gotchas, or patterns that should survive beyond the current conversation. For long-term workspace memory, prefer mempalace.