Loading...
Loading...
Found 18 Skills
Write a new doc-site page (guide, tutorial, reference, concept) following the project's docs conventions. Use when user says 'write a doc', 'add a page to the docs site', 'create a guide for X', 'write a tutorial', 'document this concept', or 'add reference for our API'. Do NOT use for feature-specific end-user docs (use document-feature), ADRs (use document-decision), or CLAUDE.md updates (use create-or-audit-claude-md).
Use this skill when writing a PRD for a feature.
Break a feature spec into intentional waves and bite-sized tasks grouped by dependency. Use after a spec is written to prepare for easy-to-track implementation.
Plan features interactively. Asks clarifying questions, then generates a detailed PRD document.
Write or update a single-feature PRD (`Type: feat`/`fix`/`chore`) with scope, user stories, and acceptance criteria. Triggers: plan prd, write feature spec, define acceptance criteria, update prd.
Project and feature planning with 4 phases - Specify, Design, Tasks, Implement+Validate. Creates atomic tasks with verification criteria and maintains persistent memory across sessions. Stack-agnostic. Use when (1) Starting new projects (initialize vision, goals, roadmap), (2) Working with existing codebases (map stack, architecture, conventions), (3) Planning features (requirements, design, task breakdown), (4) Implementing with verification, (5) Tracking decisions/blockers across sessions, (6) Pausing/resuming work. Triggers on "initialize project", "map codebase", "specify feature", "design", "tasks", "implement", "pause work", "resume work".
Turn ideas into clear, buildable specs for AI tools or stakeholder review. Use when starting features, planning projects, or when AI keeps building the wrong thing. Creates Quick Feature Specs (10-15 min) for immediate AI builds or Full Project Scopes (1-2 hours) for budget planning and contractor estimates.
Transform a feature description into a structured spec.md
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
Create detailed feature specifications with user stories, acceptance criteria, and edge cases. Use when starting a new feature or initializing a new project.
Product Requirements Document creation and feature specification writing. Use when writing PRDs, technical specs, feature documentation, or requirements. Triggers on "PRD", "product requirements", "feature spec", "technical requirements", "functional spec".
Identify underspecified areas in the current feature spec by asking up