write-spec

Convert feature ideas into structured PRDs with problem statements and requirements.

489|254|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/me2resh/apexyard --skill write-spec-me2resh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-spec
Source: https://github.com/me2resh/apexyard/tree/main/.claude/skills/write-spec
Command: npx skills add https://github.com/me2resh/apexyard --skill write-spec-me2resh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

write-spec helps you convert a vague feature idea or raw problem statement into a clear, structured PRD that a product team can execute on with shared understanding.

Core Features & Use Cases

  • Problem-to-PRD drafting: transforms feature requests into a PRD with problem statement, goals, non-goals, user stories, and requirements.
  • Context gathering: prompts for user problem, target users, success metrics, constraints, and prior art to reduce ambiguity.
  • Tool-assisted context pull: searches connected integrations (GitHub Issues, Notion/Confluence, Figma) for related work and research.
  • Iteration and handoff: generates a draft, lets you adjust sections, and positions the output for a Tech Lead feasibility review afterward.

Quick Start

Ask the AI to create a PRD by running /write-spec with your feature or problem statement, such as “SSO support for enterprise.”

Frequently Asked Questions about write-spec

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

FAQPage Schema
How do I convert a feature idea into a product requirements document?▼

Converting a feature idea into a product requirements document requires gathering conversational context on target users and constraints, resolving a PRD template, and outputting a handoff-ready draft with clear acceptance criteria.

What is the best way to define user stories and acceptance criteria for a new initiative?▼

The best way to define user stories and acceptance criteria is through structured product discovery that prompts for success metrics, target users, and constraints, mapping the gathered context into a standardized feature specification format.

Can I pull related context from Notion or Figma when creating a feature specification?▼

Yes, you can pull related context from Notion, Confluence, or Figma when creating a feature specification by using tool-assisted context pulling to search connected integrations for prior art and related research.

Does this approach require a specific role activation for product discovery?▼

Yes, product discovery and PRD creation require role activation for the Product Manager to properly resolve PRD templates, gather conversational context, and structure the final handoff-ready draft.

How do I prepare a PRD draft for a Tech Lead feasibility review?▼

Preparing a PRD draft for a Tech Lead feasibility review involves iterating on generated sections to adjust goals and non-goals, ensuring the final feature specification positions the output clearly for downstream technical validation.

What should I include in a PRD to ensure stakeholder alignment?▼

To ensure stakeholder alignment, a PRD should include a clear problem statement, explicitly defined goals and non-goals, structured user stories, and measurable success metrics gathered during the context collection phase.