feature-spec

Draft structured PRDs with YAML frontmatter and defined templates.

1|Updated Mar 9, 2026

Search Tags:#documentation #prioritization #prd #user-stories #acceptance-criteria #feature-spec #prds

Ready to run

npx skills add https://github.com/kiryteo/opencode-setup --skill feature-spec-kiryteo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-spec
Source: https://github.com/kiryteo/opencode-setup/tree/main/skills/feature-spec
Command: npx skills add https://github.com/kiryteo/opencode-setup --skill feature-spec-kiryteo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing PRDs and feature specifications is error-prone and time-consuming without a structured template that ensures alignment across product, design, and engineering teams.

Core Features & Use Cases

Standardized PRD templates that cover Problem Statement, Goals, Non-Goals, User Stories, Requirements, Success Metrics, Open Questions, and Timeline.
Guidance on writing clear acceptance criteria using Given/When/Then and testable criteria.
Support for documenting user stories in standard format (As a [user], I want [capability] so that [benefit]).
Prioritization guidance with MoSCoW (Must, Should, Could, Won't) to shape phased delivery.
Built-in rationale and decision documentation for traceability and future reference.

Quick Start

Draft a complete PRD for a new feature that enables offline syncing in a mobile app.

Frequently Asked Questions about feature-spec

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

FAQPage Schema

How do I write a PRD that aligns product, design, and engineering teams?▼

Drafting a PRD with a standardized template ensures alignment across product, design, and engineering by structuring problem statements, goals, non-goals, user stories, requirements, and success metrics into a single cohesive document.

What is the best way to format acceptance criteria for feature specifications?▼

The best way to format acceptance criteria is using the Given/When/Then structure to create clear, testable conditions. This method defines specific scenarios, ensuring engineering teams understand exactly how to validate feature behavior and success.

How do I prioritize features for phased delivery in a product specification?▼

Prioritize features for phased delivery by applying the MoSCoW method, which categorizes requirements into Must, Should, Could, and Won't tiers. This framework helps shape delivery phases and clarifies scope boundaries across teams.

Can I use standard user stories and metadata in my feature specs?▼

Yes, feature specs support standard user story formats like 'As a [user], I want [capability] so that [benefit]' and include YAML frontmatter metadata. This combination provides traceability and structured context for engineering and design teams.

How do I document decision rationale within a feature spec?▼

Document decision rationale within the feature spec by utilizing built-in rationale sections and open questions fields. This ensures traceability and provides future reference for product, design, and engineering teams regarding scope and prioritization choices.

What should I include in a PRD to prevent scope creep during development?▼

To prevent scope creep, a PRD should explicitly define non-goals alongside goals, use MoSCoW prioritization for requirements, and detail open questions. Clarifying these boundaries aligns product and engineering teams on what is excluded from the current phase.