specify-feature

Name: specify-feature
Availability: InStock
Author: patrickrmoore

Identify valid Skill Units and extract metadata into structured YAML.

Updated Mar 22, 2026

Search Tags:#workflow #planning #specification #governance #feature #product-management

Ready to run

npx skills add https://github.com/patrickrmoore/sdd-test --skill specify-feature

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: specify-feature
Source: https://github.com/patrickrmoore/sdd-test/tree/main/.github/skills/specify-feature
Command: npx skills add https://github.com/patrickrmoore/sdd-test --skill specify-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Specify Feature workflow provides a repeatable, governance-friendly process to transform natural language feature requests into a structured specification document, ensuring consistency, traceability, and alignment with stakeholder context.

Core Features & Use Cases

Centralized workflow: Acquire context, detect type, load product doc, perform research, generate spec, validate, and report.
Reusable outputs: Produces specs in spec.md with frontmatter fields (SPEC_TYPE, EPIC_ID, EPIC_SOURCES) and a detailed body aligned to the chosen type (product/technical/operational).
Collaboration-ready: Integrates with project planning and product docs; supports autopilot and NEEDS CLARIFICATION workflows to reduce cycle time.

Quick Start

Describe the feature you want to specify to start the specification workflow.

Frequently Asked Questions about specify-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn natural language ideas into structured feature specifications?▼

You can generate a structured feature specification by providing a natural language description of your idea, which triggers a workflow to acquire context, detect the spec type, load product docs, and output a spec.md file.

What is the best way to create traceable product specifications from stakeholder requests?▼

The best way to create traceable product specifications is using a governance-friendly workflow that captures stakeholder context, integrates with product docs, and outputs a structured spec.md with traceable EPIC_ID fields.

Can I generate different types of specification documents from a single feature request?▼

Yes, you can generate product, technical, or operational specification documents. The workflow detects the appropriate spec type from your natural language input and structures the detailed body to match.

How do I handle ambiguous feature requests during product specification generation?▼

Ambiguous feature requests trigger a NEEDS CLARIFICATION workflow within the specification process. This pauses generation to request missing context from stakeholders, ensuring alignment before producing the final spec.

Does the feature specification workflow support autopilot for generating product docs?▼

Yes, the feature specification workflow supports an autopilot mode. This automates context acquisition, research, and spec generation to reduce manual intervention and accelerate product documentation cycles.

What metadata is included in a generated feature specification document?▼

Generated feature specification documents include spec.md frontmatter fields like SPEC_TYPE, EPIC_ID, and EPIC_SOURCES. The document body is then detailed and aligned to the chosen product, technical, or operational type.