OpenParable
Skip to content
← Back to skills

Feature Spec

Business
feature-spec

Feature Spec is an Agent Skill for business published in the davepoon/buildwithclaude repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/davepoon/buildwithclaude/blob/HEAD/plugins/agent-triforce/skills/feature-spec/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/feature-spec, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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