Draft structured PRDs with YAML frontmatter and defined templates.
npx skills add https://github.com/kiryteo/opencode-setup --skill feature-spec-kiryteo
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
Writing PRDs and feature specifications is error-prone and time-consuming without a structured template that ensures alignment across product, design, and engineering teams.
Draft a complete PRD for a new feature that enables offline syncing in a mobile app.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
niconiahiConvert a problem statement into a structured PRD with goals and success metrics.
ramybarsoumConvert approved Feature Doc Section 5 use cases into engineering tickets for Linear, Jira, or text.
ivegamsftProvide UX design templates and checklists for journey mapping, wireframing, and accessibility auditing.
cubetribeBypass production quality gates for disposable local prototyping experiments.
