feature-spec

Solid

Creates a complete product feature specification with acceptance criteria, scope, dependencies, and risks. Delegates to the Prometeo (PM) agent.

Testing & QA 2,987 stars 362 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
71
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Feature Spec Creates a complete product feature specification using the Prometeo (PM) agent. ## When to Use This Skill - Defining a new feature or product requirement - Writing user stories with acceptance criteria - Planning product work that needs a structured spec - Documenting business requirements before implementation ## What This Skill Does 1. Runs the SIGN IN checklist (identity, task, memory review) 2. Researches existing specs to avoid conflicts 3. Creates a comprehensive spec at `docs/specs/{feature-name}.md` 4. Runs the Spec Completion checklist (TIME OUT) 5. Prepares a structured handoff to the Dev agent 6. Runs the SIGN OUT checklist (memory update, deliverables) ## How to Use ### Basic Usage ``` /feature-spec user authentication with JWT tokens ``` ### Detailed Usage ``` /feature-spec multi-tenant billing system with Stripe integration ``` ## Example **User**: `/feature-spec webhook event system` **Output**: A complete spec at `docs/specs/webhook-event-system.md` containing: - Problem statement and success metrics - User stories with GIVEN/WHEN/THEN acceptance criteria - In-scope and out-of-scope items - Dependencies, risks, and open questions - Handoff notes for the Dev agent ## Tips - Be specific about the feature scope in your description - The agent will ask clarifying questions rather than guess - Review the generated spec before passing to implementation

Details

Author
davepoon
Repository
davepoon/buildwithclaude
Created
10 months ago
Last Updated
4 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

implement-feature

Implements a feature from its specification. Reads the spec, designs architecture, writes code and tests. Delegates to the Forja (Dev) agent.

2,987 Updated 4 days ago
davepoon
Testing & QA Solid

cspec

Create a structured specification with testable invariants for a new feature. Researches current best practices before writing invariants. Adapts format to workflow intensity.

61 Updated today
joshft
AI & Automation Listed

specdd

Spec-driven development orchestrator that turns vague, top-of-mind feature requests into production-grade specifications before any code is written. ALWAYS use this skill whenever the user describes a feature, change, capability, screen, flow, or new component in plain language — even if they don't explicitly ask for a spec. Triggers on phrases like "build me", "make me", "add a feature", "I want to", "help me create", "implement", "let's build", "I need a", "can you make", "create a screen/page/component", or any new-feature request that lacks complete requirements (missing user stories, acceptance criteria, edge cases, error/empty/loading states, accessibility, or non-functional requirements). Interviews the user to fill gaps, applies UX/UI common sense, produces a structured spec + plan + tasks, then implements against the spec. Use this BEFORE writing any code for non-trivial features. Skip only for true one-liners (rename a variable, fix a typo, answer a research question) or work that is purely investig

1 Updated today
mnyok9939
Testing & QA Solid

project-specification

Transforms project briefs into testable specifications with user stories and acceptance criteria. Use after brainstorming, before planning.

294 Updated today
athola
Code & Development Listed

spec

Write a feature spec — the "what & why" of a kandev product feature, before coding. Use ONLY for a product-feature surface (user-visible capability the app supports). Do NOT use for bug fixes, incident postmortems, refactors that preserve behavior, or infra-only work — those get ADRs (if a new convention emerged) and/or regression tests, not specs. Use when the user says "let's spec X" or starts a new product feature.

298 Updated today
kdlbs