dev-doc-master

Author and maintain PRD, DESIGN, Phase, BUSINESS_RULES, and GAPS documentation sets.

3|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/wopal-cn/wopal-space-ontology --skill dev-doc-master-wopal-cn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-doc-master
Source: https://github.com/wopal-cn/wopal-space-ontology/tree/main/skills/dev-doc-master
Command: npx skills add https://github.com/wopal-cn/wopal-space-ontology --skill dev-doc-master-wopal-cn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Product documentation sets (PRD, DESIGN, Phase, BUSINESS_RULES, GAPS) drift out of sync with each other and with the actual code, producing broken links, duplicated facts, and stale architecture claims. This Skill enforces a single consistent rule set and a mandatory quality gate so every document in the set stays aligned with the repository. ## Core Features & Use Cases - Document authoring and routing: Create or update PRD, product/project DESIGN, sub-DESIGNs, Phase/Roadmap, BUSINESS_RULES, and GAPS documents using dedicated references and templates, routed from /cupdate-* commands. - Consistency enforcement: Apply universal rules — no chapter numbering, relative links only, header-vs-reference link separation, bidirectional sub-document indexes, target-state writing, and fixed header field vocabulary. - Gap tracking: Record design-to-implementation divergence in GAPS.md with bounded-enumeration discovery, Current/Target/Design/Exit entries, and immutable identifiers. - Use Case: After reworking a design, ask to update the DESIGN doc; the Skill splits oversized documents into sub-DESIGNs, aligns PRD and Phase documents, and runs scripts/verify-docset.py until the quality gate passes. ## Quick Start Ask the assistant to update the project DESIGN document and align the rest of the documentation set using the dev-doc-master skill.

Frequently Asked Questions about dev-doc-master

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

FAQPage Schema
How do I split a large DESIGN document into sub-documents?

Split when the main DESIGN exceeds roughly 500 lines or a single chapter exceeds 150 lines. Create DESIGN-<topic>.md files in the same directory, give each a Parent link to ./DESIGN.md, and enumerate them in the main header's Sub-DESIGNs field.

What is the difference between a gap and an issue in GAPS.md?

A gap records an unimplemented design contract, a design change the code has not followed, or an experimental design area. A satisfied contract with a bug is an issue tracked through the issue workflow, not a gap.

When should I use dev-doc-master versus dev-flow?

Use dev-doc-master for authoring and aligning PRD, DESIGN, Phase, BUSINESS_RULES, and GAPS documents. Use dev-flow for writing development Plans, df-implement-review for reviewing implementation code, and space-master for project README files.

Can a GAPS document measure against a draft design?

No. Only formal documents with Active status participate in GAPS analysis. A Draft or Proposed design must be promoted to Active first, because a gap measures distance from a settled target state.

Why does the documentation quality gate fail on my update?

The verify-docset.py script fails on mismatched Sub-DESIGNs enumeration versus actual files, missing Parent links, absolute paths, broken relative links, header documents repeated in the Reference Documents section, process-state vocabulary like deprecated or legacy, and missing Updated dates.