Skip to content
Back to skills

Feature Spec

ASecurity

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

  • 3,543 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 29, 2026
ai-agentsgo

Security analysis

A100/100

Scanned May 29, 2026

npx -y skills add davepoon/buildwithclaude --skill feature-spec --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Feature Spec?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Feature Spec
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/davepoon-feature-spec/badge)](https://www.skillsdirectory.com/skills/davepoon-feature-spec)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: feature-spec
category: workflow-orchestration
description: Creates a complete product feature specification with acceptance criteria, scope, dependencies, and risks. Delegates to the Prometeo (PM) agent.
---

# 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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…