kiro-spec-designlisted

# kiro-spec-design Skill ## Core Mission - **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 ## Execution Steps ### Step 1: Gather Context If steering/spec context is already available from conversation, skip redundant file reads. Otherwise, load all necessary context: - `.kiro/specs/{feature}/spec.json`, `requirements.md`, `design.md` (if exists) - `.kiro/specs/{feature}/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 - `.kiro/settings/templates/specs/design.md` for document structure - Read `rules/design-principles.md` from this skill's directory for design principles - `.kiro/settings/templates/specs/research.md` for discovery log structure **Validate requirements approval**: - If auto-approve flag is true: Auto-approve requirements in spec.json - Otherwise: Verify approval status (stop if unapproved, see Safety & Fallback) ### St