growilabs/growi

kiro-spec-cleanup

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

kiro-review

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.

kiro-validate-impl

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

esm-merge-coverage

ESM-ify source files that arrive from a pre-ESM branch when merging into apps/app. Use after merging any branch that predates the v8 ESM migration (long-lived feature branches cut from v7-era master, v7.5 maintenance work) into master or a v8 branch — a git…

app-commands

GROWI main application (apps/app) specific commands and scripts. Auto-invoked when working in apps/app.

essential-test-design

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

suggest-path-evaluator

Evaluate the quality of GROWI's suggest-path output by judging each proposed save-path as o (usable) / △ (usable but improvable) / x (not usable) for a document, with a wiki-agnostic plausibility rubric — NOT by matching one "correct" path. For each document…

fix-broken-next-symlinks

Fix broken symlinks in .next/node_modules/ — diagnose, decide allowlist vs dependencies, and verify

mongoose-to-prisma

Migrate a single Mongoose model file to Prisma, following GROWI's established patterns. Step-by-step with human approval at each stage.

app-specific-patterns

GROWI main application (apps/app) specific patterns for Next.js, Jotai, SWR, and testing. Auto-invoked when working in apps/app.

essential-test-patterns

GROWI testing patterns with Vitest, React Testing Library, and vitest-mock-extended (type-safe mocking, avoid type assertions). Auto-invoked when writing or reviewing tests.

investigate-issue

Investigate a GitHub issue - fetch info, update labels, analyze code/reproduce, report findings, and optionally fix. Usage: /investigate-issue <issue-url-or-number>

page-transition-and-rendering-flow

Auto-invoked when modifying page transition logic, global atom hydration, or the `[[...path]]` dynamic route. Explains the data flow from SSR/client navigation to page rendering, and the hydration-vs-subsequent-sync rule for global atoms…

kiro-discovery

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.

kiro-impl

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

kiro-spec-batch

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

kiro-spec-design

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

kiro-spec-init

Initialize a new specification with detailed project description

kiro-spec-quick

Quick spec generation with interactive or automatic mode

kiro-spec-requirements

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

kiro-spec-status

Show specification status and progress

kiro-spec-tasks

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

kiro-steering-custom

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

kiro-steering

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

kiro-validate-design

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

kiro-validate-gap

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

build-optimization

GROWI apps/app Turbopack configuration, module optimization, and build measurement tooling. Auto-invoked when working in apps/app.

vendor-styles-components

Vendor CSS precompilation system for Turbopack compatibility. How to add third-party CSS to components without violating Pages Router global CSS restriction. Auto-invoked when working in apps/app.

page-save-origin-semantics

Auto-invoked when modifying origin-based conflict detection, revision validation logic, or isUpdatable() method. Explains the two-stage origin check mechanism for conflict detection and its separation from diff detection.

app-architecture

GROWI main application (apps/app) architecture, directory structure, and design patterns. Auto-invoked when working in apps/app.