Menu
PRD format conventions, boundary rules, and template references. Load when writing or reviewing product requirements.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Architectural validation checklist for feature approval. Load when validating that features fit into the existing architecture.
Architecture Decision Record format, naming conventions, and when to create ADRs. Load when making or documenting architectural decisions.
Audit the agentic configuration for consistency, coherence, and conciseness. Load when modifying agent definitions, skills, or pipeline structure, or to verify cross-tool parity.
Build, test, format, and lint requirements that must pass before code review. Load when checking implementation completeness or running the quality gate.
Go code quality checklist based on Google Go Style Guide. Load when conducting code quality reviews.
Pre-commit safety checks for secrets, credentials, local settings, and sensitive file patterns. Load before committing or when reviewing staged changes for accidental exposure.
| name | prd-authoring |
| description | PRD format conventions, boundary rules, and template references. Load when writing or reviewing product requirements. |
| compatibility | ["claude-code","opencode","github-copilot"] |
| metadata | {"version":"1.0","author":"team"} |
The PRD lives at docs/prd.md.
The PRD describes what the system does. It must not contain how.
Litmus test: If it would change when switching from Go to Rust, it belongs in docs/system-design.md, not the PRD.
When the PRD needs to reference implementation details:
**Implementation:** See [system-design.md#section](system-design.md#section)
| Pattern | Severity | Fix |
|---|---|---|
Go code blocks (```go) | Critical | Move to system-design.md, link from PRD |
Go function signatures (func (, chan [, *Type) | Critical | Describe behavior, not mechanism |
| Internal code references (function names, variable names) | High | Use behavioral language |
| Algorithm formulas or pseudocode | High | State behavioral constraints, move formulas to system-design.md |
| Go-specific constructs (channels, goroutines, tickers, mutexes) | High | Describe behavior, not mechanism |
| Hardcoded constant values | Medium | Reference system-design.md#constants |
Use the "Parseable Section Templates" requirement format in docs/documentation.md.
When a feature is approved, write the scope to .scratch/current-feature.md using the template in .claude/templates/current-feature.md.
Follow the Writing Standards section in docs/documentation.md.