spec-to-prd

Converts specifications, tenders, and RFPs into glossaries, translations, and traceable PRDs.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Pgooone/oh-pgone-claudecode --skill spec-to-prd-pgooone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-to-prd
Source: https://github.com/Pgooone/oh-pgone-claudecode/tree/main/.claude/skill/spec-to-prd
Command: npx skills add https://github.com/Pgooone/oh-pgone-claudecode --skill spec-to-prd-pgooone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Dense technical documents like tenders, RFPs, and procurement specifications are hard to act on: requirements are buried, terminology is inconsistent, and translation introduces errors. This Skill turns such documents into a chain of five cross-referenced artifacts so bid and delivery teams can analyze, translate, and build from them with full traceability. ## Core Features & Use Cases - Five-artifact pipeline: Produces a structured text parse, bilingual glossary, technical analysis with risk flagging, faithful translation, and an exhaustive requirements PRD with FR/NFR IDs, priorities, and acceptance criteria. - Traceability and risk management: Every PRD requirement links back to source sections via a traceability matrix, and contradictions or ambiguities are collected as open items rather than silently resolved. - Use Case: A bid team receives a 200-page procurement specification in French. The Skill parses it section by section, builds a French-to-English glossary, flags contradictory retention periods, translates the document, and delivers a PRD with P0/P1/P2 requirements ready for estimation. ## Quick Start Analyze the attached tender document, translate it into English, and produce a PRD with a traceability matrix.

Frequently Asked Questions about spec-to-prd

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

FAQPage Schema
How do I extract requirements from an RFP or tender document?▼

Provide the document and request requirement extraction. The Skill parses the source section by section, captures every must/shall/should statement with quantitative thresholds, and produces a PRD where each requirement has an ID, priority, and acceptance check.

How to write a PRD from a procurement specification?▼

Hand the specification to the Skill and ask for a PRD. It runs a pipeline of parsing, glossary building, technical analysis, and translation, then generates a PRD with functional and non-functional requirements, delivery phases, and a traceability matrix.

Can I request only one artifact like a glossary or translation?▼

Yes. Partial requests such as translating a spec or building a glossary are supported, and stages irrelevant to the document are skipped. The Skill will offer the remaining artifacts since they reinforce each other.

What document types does spec-to-prd support?▼

It handles specifications, tenders, RFPs, bids, procurement documents, contracts, vendor datasheets, and other requirements-heavy documents. It is domain-neutral and derives all terminology and structure from the source document itself.

How does it handle contradictions in the source document?▼

Contradictions are flagged, not fixed. Each conflict is recorded as an open item with references to both source sections, and these items carry through the analysis into the PRD so they stay visible for estimation and acceptance.

Does the translation handle machine-translated source documents?▼

Yes. The Skill watches for mangled symbols, false friends, and unit errors common in machine-translated sources, restores intended symbols where possible, and marks suspected artifacts with translator notes instead of trusting them silently.