writing-spec-documents

Generate living implementation specification documents with traceability to PRD/FR references.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/WesleyMFrederick/cc-workflows-plugin --skill writing-spec-documents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-spec-documents
Source: https://github.com/WesleyMFrederick/cc-workflows-plugin/tree/main/src-claude/skills/writing-spec-documents
Command: npx skills add https://github.com/WesleyMFrederick/cc-workflows-plugin --skill writing-spec-documents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and maintain implementation specification documents that evolve with sequencing and implementation, ensuring traceability to whiteboard decisions and PRD/FR references.

Core Features & Use Cases

  • Living document that evolves during sequencing and implementation.
  • Enforces traceability to whiteboard decisions, PRDs, and FRs.
  • Structured frontmatter entry and XML-based component templates to guide development.

Quick Start

Announce at the start: I'm using the writing-spec-documents skill to create the implementation spec.

Frequently Asked Questions about writing-spec-documents

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

FAQPage Schema
How do I create implementation specification documents that maintain traceability to PRD references?

Implementation specification documents maintain traceability by enforcing structured frontmatter entry points and XML component templates that link design decisions directly back to PRD and FR references. This ensures every specification component maps to original product requirements.

What is a living specification document and when do I need one during the development phase?

A living specification document is an evolving implementation spec that updates during sequencing and implementation rather than remaining static. You need one during Phase 2 and beyond when whiteboard decisions and design choices must stay traceable throughout development.

How do I structure an implementation spec to trace whiteboard decisions through to development?

Structure implementation specs using frontmatter-driven entry points and XML-based component templates that enforce standardized acceptance criteria traceability. This format links each sequencing decision and design component back to original whiteboard decisions.

Can I use standardized acceptance criteria traceability with existing PRD and FR references?

Standardized acceptance criteria traceability works with existing PRD and FR references by mapping each XML component template back to those original documents. The frontmatter entry point ensures all design and sequencing decisions remain linked to established requirements.

What's the best way to keep specification documents synchronized as implementation evolves?

The best way to keep specification documents synchronized is using a living document approach applied during Phase 2 and beyond. It maintains continuous traceability to whiteboard decisions and PRD references as sequencing and implementation progress.

Why does my specification document lose traceability to whiteboard decisions during implementation?

Specification documents lose traceability when they lack enforced frontmatter entry points and XML component templates. Without standardized acceptance criteria traceability linking design decisions to whiteboard decisions, connections to original PRD references break as implementation evolves.