growi

Write tests that verify observable behavior (contract), not implementation details. Auto-invoked when writing or reviewing tests.

GROWI testing patterns with Vitest, React Testing Library, and vitest-mock-extended.

Show specification status and progress

Quick spec generation with interactive or automatic mode

Implement approved tasks using TDD with native subagent dispatch. Runs all pending tasks autonomously or selected tasks manually.

Analyze implementation gap between requirements and existing codebase. Use when planning integration with existing systems.

Generate implementation tasks from requirements and design. Use when creating actionable task lists.

Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process. Use when creating architecture from requirements.

Initialize a new specification with detailed project description

Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.

Generate EARS-format requirements based on project description and steering context. Use when generating requirements from project description.

Interactive technical design quality review and validation. Use when reviewing design before implementation.

GROWI technology stack, build tools, and global commands. Auto-invoked for all GROWI development work.

Entry point for new work. Determines the best action path or work decomposition (update existing spec, create new spec, mixed decomposition, or no spec needed) and refines ideas through structured dialogue.

Create custom steering documents for specialized project contexts. Use when creating domain-specific steering files.

Organize and clean up specification documents after implementation completion. Removes implementation details while preserving essential context for future refactoring.

Investigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.

Review a task implementation against approved specs, task boundaries, and verification evidence. Use after an implementer finishes a task, after remediation, or before accepting a task as complete.

Validate feature-level integration after all tasks are implemented. Checks cross-task consistency, full test suite, and overall spec coverage.

Maintain .kiro/steering/ as persistent project memory (bootstrap/sync). Use when initializing or updating steering documents.

GROWI monorepo structure, workspace organization, and architectural principles. Auto-invoked for all GROWI development work.

Create complete specs (requirements, design, tasks) for all features in roadmap.md using parallel subagent dispatch by dependency wave.

/learn - Pattern Extraction for GROWI

Enforce test-driven development workflow. Scaffold interfaces, generate tests FIRST, then implement minimal code to pass. Ensure 80%+ coverage.