5d-skills

Execute implementation tasks with quality and awareness. Use when: (1) After TASKS phase in 5D-SDD workflow, (2) Tasks are defined and sequenced, (3) User is ready to write code, (4) User asks to 'implement,' 'build,' or 'code' a task. This phase produces working code while maintaining connection to spec intent.

Analyze the gap between current state and specification to identify all required changes. Use when: (1) After SPEC phase in 5D-SDD workflow, (2) Spec exists and implementation is about to begin, (3) User asks 'what needs to change' or 'what's the delta,' (4) Assessing scope of work. This phase prevents surprise discoveries during implementation.

Pre-development orientation and assumption mapping for spec-driven development. Use when: (1) Starting a new feature or project, (2) User says 'let's build X' without prior analysis, (3) Beginning any 5D-SDD workflow, (4) User wants to 'think through' an idea before planning. This phase prevents wasted effort by surfacing hidden assumptions and identifying all relevant domains before committing to a direction.

Convert expanded thinking into a concrete, multi-perspective plan. Use when: (1) After SPAR phase in 5D-SDD workflow, (2) User is ready to define what will be built, (3) User asks to 'write up the plan' or 'document what we're building,' (4) Transitioning from exploration to commitment. This phase creates the authoritative description of intent before technical specification.

Stress-test the plan through adversarial review and edge case analysis. Use when: (1) After PLAN phase in 5D-SDD workflow, (2) User wants to 'validate,' 'review,' or 'check' a plan, (3) Before committing significant resources to implementation, (4) Plan exists but hasn't been challenged. This phase catches plan-level errors before they become code-level errors.

Extract learning from completed work to improve future cycles. Use when: (1) After VERIFY phase shows feature complete, (2) End of development iteration, (3) User asks for 'retrospective,' 'lessons learned,' or 'what went well/wrong,' (4) Before starting next major feature. This phase prevents repeating mistakes and compounds learning.

5D Spec-Driven Development - A complete methodology for building software through structured phases. Use when: (1) User wants to build something non-trivial, (2) User mentions '5D' or 'spec-driven development,' (3) Starting a new project or feature that needs careful planning, (4) User wants a structured approach to development. This skill orchestrates the full workflow across 10 phases from orientation to reflection.

Structured sparring to challenge and expand thinking before planning. Use when: (1) User has an idea but hasn't stress-tested it, (2) After ORIENT phase in 5D-SDD workflow, (3) User asks to 'think through,' 'challenge,' or 'poke holes' in an idea, (4) User seems certain too early—needs perspective expansion. This phase prevents building the wrong thing by forcing multi-perspective examination.

Convert refined plan into technical specification with architectural decisions. Use when: (1) After REFINE phase in 5D-SDD workflow, (2) User is ready for technical design, (3) Moving from 'what' to 'how,' (4) User asks for 'technical spec,' 'architecture,' or 'design doc.' This phase bridges business intent and implementation detail.

Break gap analysis into sequenced, actionable tasks. Use when: (1) After GAP ANALYSIS phase in 5D-SDD workflow, (2) User is ready to start implementation, (3) Gaps are identified but not yet organized into work items, (4) User asks for 'task list,' 'breakdown,' or 'what to do first.' This phase creates the implementation roadmap.

Strategic multi-dimensional thinking framework for analysis and problem-solving. Use when tasks require: (1) Complex problem analysis, (2) Breaking through mental limitations, (3) Evaluating ideas from multiple perspectives, (4) Understanding root causes, (5) Generating novel insights, (6) Strategic planning, or when the user asks for deep analysis, wisdom, creative solutions, or references '5D thinking,' 'multi-dimensional analysis,' or 'strategic genius' thinking.

Multi-layer verification of implementation against spec and intent. Use when: (1) After BUILD phase in 5D-SDD workflow, (2) Implementation is complete and needs validation, (3) User asks to 'test,' 'verify,' or 'check' the implementation, (4) Before considering a feature done. This phase catches errors at multiple levels and routes fixes appropriately.