| name | ct-spec-writer |
| description | Technical specification writing using RFC 2119 language for clear, unambiguous requirements. Creates protocol specifications, technical requirements, API specifications, and architecture documents with testable requirements and compliance criteria. Use when writing specifications, defining protocols, documenting requirements, or creating API contracts. Triggers on specification tasks, protocol definition needs, or requirement documentation. |
| version | 2.1.0 |
| tier | 2 |
| core | false |
| category | recommended |
| protocol | specification |
| loomStage | specification |
| adrRefs | ["ADR-014","ADR-023"] |
| dependencies | [] |
| sharedResources | ["subagent-protocol-base","task-system-integration"] |
| compatibility | ["claude-code","cursor","windsurf","gemini-cli"] |
| license | MIT |
Specification Writer Context Injection
Protocol: @src/protocols/specification.md
Type: Context Injection (cleo-subagent)
Version: 2.0.0
Purpose
Context injection for specification writing tasks spawned via cleo-subagent. Provides domain expertise for creating clear, unambiguous technical specifications using RFC 2119 language.
Capabilities
- Protocol Specifications - Define behavior rules with RFC 2119 keywords
- Technical Requirements - Document system requirements with constraints
- API Specifications - Define interfaces, schemas, and contracts
- Architecture Documents - Document system design decisions
RFC 2119 Keywords (MANDATORY)
Use these keywords with their precise meanings:
| Keyword | Meaning | Compliance |
|---|
| MUST | Absolute requirement | 95-98% |
| MUST NOT | Absolute prohibition | 93-97% |
| SHOULD | Recommended unless good reason exists | 75-85% |
| SHOULD NOT | Discouraged unless good reason exists | 75-85% |
| MAY | Truly optional | 40-60% |
Specification Structure
Standard Layout
# {Specification Title} v{X.Y.Z}
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document
are to be interpreted as described in RFC 2119.
---
## Overview
{2-3 sentence summary of what this spec defines}
---
## Definitions
| Term | Definition |
|------|------------|
| {term} | {definition} |
---
## Requirements
### {Category 1}
**REQ-001**: {Requirement description}
- Rationale: {Why this requirement exists}
- Verification: {How to verify compliance}
### {Category 2}
: {Requirement description}
...
---
| ID | Constraint | Enforcement |
|----|------------|-------------|
| CON-001 | {constraint} | {how enforced} |
---
A system is compliant if:
{condition 1}
{condition 2}
{condition 3}
Non-compliant implementations SHOULD {remediation}.
