Technical Design Generator

Technical Design Generator

<background_information>

• Success Criteria:
  • All requirements mapped to technical components with clear interfaces
  • The design makes responsibility boundaries explicit enough to guide task generation and review
  • Appropriate architecture discovery and research completed
  • Design aligns with steering context and existing patterns
  • Visual diagrams included for complex architectures </background_information>

Step 1: Load Context

Read all necessary context:

• {{KIRO_DIR}}/specs/$1/spec.json, requirements.md, design.md (if exists)
• {{KIRO_DIR}}/specs/$1/research.md (if exists, contains gap analysis from @kiro-validate-gap)
• Core steering context: product.md, tech.md, structure.md
• Additional steering files only when directly relevant to requirement coverage, architecture boundaries, integrations, runtime prerequisites, security/performance constraints, or team conventions that affect implementation readiness
• Use explicitly requested skills and task-relevant local skills/playbooks, including design, accessibility, and UX. Select by description and read only needed guidance, even for small tasks; preserve required checks and host/project rules.
• Consult relevant domain skills even when building by hand without adopting a new library.
• {{KIRO_DIR}}/settings/templates/specs/design.md for document structure
• Read rules/design-principles.md from this skill's directory for design principles
• {{KIRO_DIR}}/settings/templates/specs/research.md for discovery log structure

Validate requirements approval:

• If -y flag provided ($2 == "-y"): Auto-approve requirements in spec.json
• Otherwise: Verify approval status (stop if unapproved, see Safety & Fallback)

Step 2: Discovery & Analysis

Critical: This phase ensures design is based on complete, accurate information.

1. Classify Feature Type:
   • New Feature (greenfield) → Full discovery required
   • Extension (existing system) → Integration-focused discovery
   • Simple Addition (CRUD/UI) → Minimal or no discovery
   • Complex Integration → Comprehensive analysis required