Can I update an existing specification with this skill?

Yes, using the --update flag allows you to refine or expand existing specifications as project requirements evolve.

Why does OpenCode Specify exclude implementation details?

By focusing strictly on 'What' and 'Why', the skill prevents premature technical constraints and ensures the architecture lead has full context to choose the best implementation path later.

Where does the skill store the generated specifications?

Specifications are organized within the .opencode/specs/ directory, using a slug-based folder structure that includes the spec file and a clarification log.

How does the skill handle ambiguous requirements?

It uses a specific 'NEEDS CLARIFICATION' syntax to flag uncertainties. If more than three markers are found, it automatically triggers a clarification workflow.

OpenCode Specify

Name: OpenCode Specify
Author: peterstorm

bypeterstorm

0•

생산성 및 워크플로

Translates high-level feature requests into formal, technology-agnostic specifications to guide architecture and development.

OpenCode Specify is a foundational tool for the development lifecycle that formalizes raw ideas into structured requirements. By focusing exclusively on the 'What' and 'Why' of a feature, it ensures that user scenarios, functional requirements, and success criteria are clearly defined before any technical implementation begins. This skill forces a strict separation between requirements and architecture, preventing premature technical decisions and identifying ambiguities through an automated clarification trigger. It produces standardized Markdown documentation that serves as the single source of truth for subsequent architecture and task planning phases.

주요 기능

01Automatically identifies and flags requirements needing clarification for further research

02Establishes measurable and verifiable success criteria for feature validation

03Enforces a strict 'No Implementation Details' constraint to prevent design bias

04Generates structured, technology-agnostic Markdown specifications in .opencode/specs/

050 GitHub stars

06Defines user scenarios with prioritized P1-P3 acceptance criteria

사용 사례

01Creating clear project boundaries by explicitly defining out-of-scope items

02Formalizing business requirements before moving to technical architecture design

03Capturing user scenarios and success metrics for non-trivial feature requests

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add peterstorm/.dotfiles opencode-specify

For use in Claude.ai and ChatGPT

Download Skill