pmai-spec-writing

Compiles confirmed product decisions into module specs, PRDs, and review-ready requirement documents.

4|Updated May 26, 2026
One-click install
npx skills add https://github.com/YYG501/PM-AI-Harness --skill pmai-spec-writing-yyg501
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pmai-spec-writing
Source: https://github.com/YYG501/PM-AI-Harness/tree/main/skills/spec-writing
Command: npx skills add https://github.com/YYG501/PM-AI-Harness --skill pmai-spec-writing-yyg501

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product managers often have confirmed decisions scattered across discussions, proposals, and prototypes but lack a rigorous, review-ready specification. This Skill turns closed product decisions into authoritative module specs, functional requirement documents, or full PRDs without inventing undecided product content. ## Core Features & Use Cases - Decision-gated spec authoring: Runs proposal and active-build gates before writing, routing unresolved product-level gaps back to proposal and module-level gaps back to design. - Composable content model: Combines generic content modules (information model, core actions, exceptions, acceptance criteria) with stackable enterprise-platform and AI-product profiles, plus a single full-PRD preset and template. - Spec remediation and landed reconciliation: Optimizes existing specs, and after implementation lands, reconciles code against specs using a four-branch model (conforming, accepted delta, missing implementation, unjustified implementation). - Use Case: After a design phase closes on a tenant-management module, invoke this Skill to produce docs/modules/<module>/spec.md with information model, action details, exception paths, and acceptance criteria, then lint the PRD hierarchy before review. ## Quick Start Ask the assistant to turn the confirmed design decisions for the current module into a formal module specification document.

Frequently Asked Questions about pmai-spec-writing

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

FAQPage Schema
How do I write a PRD from confirmed product decisions?

Invoke the spec-writing skill after product direction and module design are closed. It loads the current proposal contract, selects content modules and applicable profiles, and generates the PRD from the single full-PRD preset and template.

What is the difference between a module spec and a full PRD?

A module spec (docs/modules/<module>/spec.md) is the authoritative build contract for one module. A full PRD is one form of functional specification compiled from module specs and project rules for cross-role review, not a second source of product truth.

When does spec-writing refuse to write a specification?

It stops when product-level premises (positioning, users, value, MVP) are undecided, routing to proposal, or when module objects, rules, or interactions are open, routing to design. It never fills product decisions with defaults.

Can I use this to improve an existing PRD?

Yes. The existing-spec remediation flow reads the original plus related module specs and project rules, produces a revision plan covering structure, content, and style, then rewrites without adding unconfirmed rules.

How are enterprise platform and AI product requirements handled?

Two stackable profiles add domain checks: enterprise-platform covers tenants, permissions, versioning, and audit; AI covers human-AI responsibility, evaluation, and failure degradation. Both can load together without a third combined profile.

What happens when implementation diverges from the specification?

Landed reconciliation classifies each item as conforming, accepted delta, missing implementation, or unjustified implementation. Missing or unjustified items block document updates and route back to design rather than rewriting the spec to match code.