بنقرة واحدة
kiro-spec-init
Initialize a new specification with detailed project description
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Initialize a new specification with detailed project description
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
GROWI main application (apps/app) specific patterns for Next.js, Jotai, SWR, and testing. Auto-invoked when working in apps/app.
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 (type-safe mocking, avoid type assertions). Auto-invoked when writing or reviewing tests.
Investigate a GitHub issue - fetch info, update labels, analyze code/reproduce, report findings, and optionally fix. Usage: /investigate-issue <issue-url-or-number>
GROWI main application (apps/app) specific commands and scripts. Auto-invoked when working in apps/app.
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 (`currentPathnameAtom`, `currentUserAtom`, `isMaintenanceModeAtom`).
| name | kiro-spec-init |
| description | Initialize a new specification with detailed project description |
| allowed-tools | Bash, Read, Write, Glob, AskUserQuestion |
| argument-hint | <project-description> |
.kiro/specs/{feature-name}/brief.md exists (created by /kiro-discovery), read it. The brief contains problem, approach, scope, and constraints from the discovery session. Use this to pre-fill the project description and skip clarification questions that the brief already answers..kiro/specs/ for naming conflicts. If the directory already exists with only brief.md (no spec.json), use that directory (discovery created it)..kiro/specs/[feature-name]/ (skip if already exists from discovery).kiro/settings/templates/specs/init.json.kiro/settings/templates/specs/requirements-init.md{{FEATURE_NAME}} → generated feature name{{TIMESTAMP}} → current ISO 8601 timestamp{{PROJECT_DESCRIPTION}} → from brief.md if available, otherwise $ARGUMENTSen → language code (detect from user's input language, default to en)spec.json and requirements.md to spec directoryProvide output in the language specified in spec.json with the following structure:
feature-name format with 1-2 sentence rationale/kiro-spec-requirements <feature-name>Format Requirements:
spec.json.language.kiro/settings/templates/specs/, report error with specific missing file path and suggest checking repository setupfeature-name-2) and notify user of automatic conflict resolution