Generate spec.json and requirements.md from a project description.
npx skills add https://github.com/notta50/korenani --skill kiro-spec-init-notta50
Please help me install this Agent Skill. Skill: kiro-spec-init Source: https://github.com/notta50/korenani/tree/main/.claude/skills/kiro-spec-init Command: npx skills add https://github.com/notta50/korenani --skill kiro-spec-init-notta50
Kiro spec init solves the tedious, error-prone task of creating a project specification skeleton from a brief description, ensuring consistency and fast onboarding.
Provide your project description and run the kiro-spec-init process to generate spec.json and requirements.md.
High-intent search queries and answers about installing and using this skill.
To auto-generate a project specification skeleton, provide your project description to a spec init tool to create the .kiro/specs directory structure, verify naming conflicts, and initialize spec.json and requirements.md templates.
The best way to speed up project kickoff requirements gathering is to integrate a discovery brief that pre-fills the project description, skipping clarifying questions about who has the problem and what should change.
To ensure consistent requirements.md and spec.json files across different features, use template-driven file creation that automatically injects proper placeholders and language codes during the project initialization process.
Yes, you can skip manual clarification questions when initializing a new spec if a discovery brief exists, which automatically pre-fills the project description instead of requesting necessary clarifications.
When initializing a project specification, the tool verifies no naming conflicts exist in the .kiro/specs directory before creating the folder and generating the unique feature name.
metratonAsk targeted questions to capture acceptance criteria and generate a draft brief.
qlawmarqAnalyze implementation gaps between project requirements and existing codebases.
elsa-workflowsValidate Git branch naming conventions and verify associated spec directories.
growilabsInitialize a unique spec directory with template-generated spec.json and requirements.md files.
