Loading...
Loading...
Found 23 Skills
Create a well-thought-out plan covering problem statement, goals, technical approach, and verification criteria. Use while planning / before implementing any non-trivial feature.
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.
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
Ideation: Use for /ideation or when organizing messy brain dumps into structured specs. NOT for existing tickets (use /spec instead).
Generate or sync a "Living Specification" (docs/spec.md) from source code to eliminate doc-code drift. Use when creating, updating, or reviewing architecture documentation for a directory or module. Triggers on requests like "generate spec", "create spec.md", "sync documentation", "update architecture docs", "/spec.doc", or when asked to document a codebase directory.
Conversational discovery — adapts from quick scoping (3-5 questions) to deep interviews (multi-round). Talk until we're clear, then build. Produces inline decisions; optionally saves spec.md or scope contract. Not for multi-perspective debate (use agent-room). Not for decomposing work (use task-breakdown).
Build requirements specification through structured discovery interview. Use when defining scope, gathering requirements, or specifying WHAT work should accomplish - features, bugs, refactors, infrastructure, migrations, performance, documentation, or any other work type. Triggers: spec, requirements, define scope, what to build.
Use this skill when the user needs to turn an idea into a buildable spec, write a project scope, create feature requirements, or define an MVP. Covers quick feature specs (10-15 min) for immediate AI builds and full project scopes (1-2 hours) for planning and contractor estimates.
Transform vague product or feature ideas into concrete, detailed specification documents through an interactive interview process. Use when the user wants to flesh out an idea, create a spec, write requirements, plan a product/feature/prototype, or go from "I have this idea..." to a concrete document. Works for software products, physical products, services, or any concept that needs specification.
Standard workflow for implementing features with specs and planning documents. Use when starting a new feature, planning implementation, or working on any non-trivial task.
Drives interactive requirement discovery to produce spec files. Use when the user says "spec this", "write specs", "create specs", or "run the spec skill".
Archive a completed spec-driven change. Warns on incomplete tasks, moves change to archive/ with a date prefix.