matthew-plusprogramming/monorepo

Overview

This skill authors authoritative implementation specifications (spec.md) from gathered product requirements. It produces TaskSpec, WorkstreamSpec, or coordinates MasterSpec creation depending on scope, and writes the resulting spec into the spec group folder alongside manifest.json and requirements.md. Use it after PM discovery or when refining docs to create testable, implementation-ready contracts.

How this skill works

The skill validates the spec group, reads requirements.md and manifest.json, then extracts problem statements, goals, EARS-style requirements, constraints, and open questions. It generates a spec.md with the appropriate tiered template (TaskSpec, WorkstreamSpec, or MasterSpec orchestration), maps requirements to acceptance criteria and tests, produces a task list, and appends a decision & work log entry while updating manifest.json.

When to use it

• After PM completes discovery and requirements.md exists in a spec group
• When turning product requirements into an actionable implementation contract
• To formalize acceptance criteria, task breakdown, and test plans before engineering work
• When a single workstream requires detailed design and sequence diagrams
• To coordinate multi-workstream efforts and define cross-workstream contracts

Best practices

• Do not duplicate requirements in the spec; reference requirements.md and list IDs
• Choose the spec tier by scope: TaskSpec for 30m–4h tasks, WorkstreamSpec for 4–8h deeper work, MasterSpec for 5+ workstreams
• Make acceptance criteria testable and map each to specific test files
• Include sequence diagrams and interface contracts for complex flows
• Record decisions and timestamps in Decision & Work Log and update manifest.json

Example use cases

• Author a TaskSpec for adding a logout flow: context, ACs, task list, and tests
• Create a WorkstreamSpec for a new API endpoint with sequence diagrams and data models
• Coordinate a MasterSpec that decomposes a large feature into independent workstreams and registers contracts
• Refine an existing spec after stakeholder feedback and append decisions to the log
• Produce a test plan that maps requirements to unit and integration tests for CI validation