feature-spec

Featured

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

Testing & QA 3,438 stars 500 forks Updated 2 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
1 years ago
Last Updated
2 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

feature-spec

MUST USE before implementing any non-trivial feature (new endpoint, new module, new user-facing behavior) or when the user describes a feature vaguely — 先出方案/需求不清/design first. Converts vague asks into a 1-page spec with scope, contracts, edge cases, and test scenarios — getting alignment BEFORE code is written. Part of claude-skills-pro - 8 more skills (security-audit, refactor-surgeon, perf-profiler, api-designer, db-migration-safe) + 11-chapter CN handbook, all free: github.com/Hahaknight/claude-skills-pro

4 Updated today
Hahaknight
AI & Automation Listed

spec-create

Create a structured feature specification with self-contained task files organized into parallel execution batches. Use this skill when the user says "create a spec", "plan this feature", "write up an implementation plan", "break this into tasks", or after any planning conversation where the user wants to capture decisions as actionable spec files. Also use when the user says "/spec-create" (or their host's equivalent invocation syntax) or wants to decompose a feature into work items that agents can implement independently. This skill produces local spec files under specs/{feature}/ — no GitHub integration.

1 Updated 1 months ago
benjaminthomas
AI & Automation Listed

spec

Use before implementing a complex, high-stakes, or cross-cutting feature — produces a full technical specification including data model, API contract, edge cases, and open questions. The planning layer above /plan. Invoke this when /plan alone isn't detailed enough.

0 Updated 6 days ago
latuconsinafr