Loading...
Loading...
Found 6 Skills
Use when you need to execute I1 (Implementation Plan) in the Spec Pack of sdlc-dev, convert requirements/design into `{FEATURE_DIR}/implementation/plan.md` (the single source of truth for execution checklist and status, SSOT), and provide an unambiguous task list for subsequent I2 execution.
Use when stress-testing a plan, getting grilled on a design, or before writing a PRD.
Coach an AlignFirst spec-plan-execute or AAD workflow using a CLI wrapper around a coding-agent CLI. Use when orchestrating coding agents through AlignFirst protocols non-interactively.
Spec-driven development: plan → go → review loop with spec lifecycle states and a project-level feature ledger. Use for planning features, implementing from specs, refining specs, tracking what features exist across specs, and resuming work. Trigger on requests mentioning specs, requirements/design/tasks, spec-help, spec-plan, feature ledger, FEATURES.md, spec-ledger, `.kiro`. IMPORTANT: Never edit spec files without first reading this skill.
Perform non-destructive cross-artifact consistency and quality analysis on three core documents: spec.md, plan.md, and tasks.md. Identify inconsistent, duplicate, ambiguous, and under-specified items after task generation. Trigger words include: "speckit-analyze", "speckit-analyze", "document consistency analysis", "specification analysis", "quality check", "artifact analysis", "spec analysis", "plan analysis", "task analysis"
Use when executing or continuing a spec plan interactively. Triggers on: "spec go", "execute plan", "run plan", "continue plan", "work on plan", "start plan", "run the spec". Runs tasks with configurable breakpoints for review. Pass --bg for fully autonomous background execution.