Loading...
Loading...
Found 26 Skills
This skill is used when users express the intention to develop products, applications, tools or any software projects. Collect requirements through in-depth conversations, use straightforward follow-up questions to help users clarify their ideas, and finally generate a Product Spec document (.md file) that can be directly used in Google AI Studio Builder.
Interactive feature development workflow from idea to implementation. Creates requirements (EARS format), design documents, and task lists. Triggers: "kiro", ".kiro/specs/", "feature spec", "需求文档", "设计文档", "实现计划".
Creates PRDs using persistent file-based planning. Use when user explicitly says "PRD", "product requirements document", or "产品需求文档". Combines PRD methodology with planning-with-files to avoid context switching.
Define product requirements through conversations, ask targeted questions based on selected modules, and update state.json
Plan features interactively. Asks clarifying questions, then generates a detailed PRD document.
Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.
Interactive conversation to resolve [NEEDS CLARIFICATION] markers using /speckit.clarify command. Claude asks questions about missing features, UX/UI details, behavior, and priorities. Updates specs in .specify/memory/ with answers to create complete, unambiguous documentation. This is Step 5 of 6 in the reverse engineering process.
In plan mode, this should be triggered when the user wants to build something. In this mode, you should ask a lot of questions to extract every detail, assumption, and blind spot from the user's head before proposing a structured plan.
Facilitates collaborative design exploration before implementation. Explores user intent, constraints, and requirements through structured dialogue, then produces an approved design document. Must be invoked when entering plan mode or planning any implementation. Triggers: brainstorm, design, plan, "let's think through," "how should we build."
Unified skill that guides spec creation through structured, interactive process.
Initialize and scaffold a new project with structured requirements gathering. Use when starting a project from scratch, after running a framework initializer (npm init, create-next-app, etc.), or when an existing minimal project needs proper structure, documentation, and conventions. Triggers on: 'bootstrap project', 'start new project', 'scaffold project', 'initialize project', 'setup new project', or when the user wants to go from zero to a well-structured project foundation.
This skill should be used when the user asks to "create an implementation plan", "plan a feature", "create detailed plan", "analyze requirements", or needs comprehensive project planning with requirements gathering and architectural analysis.