governance-spec-technical-writer

Converts PRDs into SPEC.json and SPEC.md with tasks and acceptance criteria.

Updated Jan 6, 2026

Search Tags:#automation #documentation #specification #governance #prd #sprints

Ready to run

npx skills add https://github.com/cslsoftwares/ParamentersORM --skill governance-spec-technical-writer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: governance-spec-technical-writer
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/governance-spec-technical-writer_V1.0.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill governance-spec-technical-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts approved PRDs into actionable SPECs (SPEC.json + SPEC.md) broken down into sprints, features, steps, edge cases, and acceptance criteria, enabling automated execution by agents.

Core Features & Use Cases

Decomposes business requirements from PRD into structured SPECs (SPEC.json and SPEC.md) with explicit sprinting, features, steps, edge cases, and acceptance criteria.
Populates technical fields (api_endpoint, build, database, auth, frontend, delphi_component, fpc_component) or flags them as gaps for input.
Produces a standard format suitable for governance review and automation pipelines across teams.

Quick Start

Convert an approved PRD into a complete SPEC.json and SPEC.md ready for agent orchestration.

Frequently Asked Questions about governance-spec-technical-writer

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

FAQPage Schema

How do I convert an approved PRD into an executable SPEC for sprint planning?▼

Converting a PRD into an executable SPEC involves decomposing business requirements into structured SPEC.json and SPEC.md files, mapping them to sprints, features, steps, edge cases, and acceptance criteria for agent execution.

What is a SPEC.json file used for in automated governance workflows?▼

A SPEC.json file is used in governance workflows to provide a structured, machine-readable format of approved PRDs, enabling automated execution by agents and standardizing reviews across teams.

How do I map PRD requirements to acceptance criteria and edge cases?▼

Mapping PRD requirements to acceptance criteria and edge cases requires decomposing the PRD into specific features and steps, ensuring each step has defined edge cases and acceptance criteria within the generated SPEC.md structure.

How are missing technical fields like api_endpoint and database handled during PRD to SPEC conversion?▼

Missing technical fields like api_endpoint, build, database, auth, frontend, delphi_component, and fpc_component are either populated if available or explicitly flagged as gaps for pending input during the PRD to SPEC conversion.

Can I use PRD to SPEC automation for sprint-based feature decomposition?▼

Yes, you can use PRD to SPEC automation for sprint-based feature decomposition, breaking down approved business requirements into actionable sprints, features, and steps suitable for agent orchestration.

What is the best way to structure technical specifications for automated agent execution?▼

The best way to structure technical specifications for automated agent execution is generating a standard SPEC format containing sprints, features, steps, edge cases, and acceptance criteria, ensuring all technical fields are populated or flagged.