Technical Design Document (RFC / ADR) Generation
Generate thorough, engineering-ready Request for Comments (RFC) and Architecture Decision Records (ADRs).
Generate comprehensive engineering RFCs and ADRs featuring goals/non-goals, trade-off comparison matrices, security reviews, and rollout plans.
Execution Workflow Procedure
Ordered steps the coding agent executes when performing this skill.
Define Goals and Non-Goals
Specify functional and operational success metrics while explicitly establishing non-goals to prevent scope creep.
Architectural Specification & Data Models
Detail component interactions, sequence flows, database schema changes, and API contracts.
Compare Alternative Technical Approaches
Construct a comparative trade-off matrix evaluating at least two alternatives across complexity, cost, and scalability.
Plan Rollout, Security, and Observability
Detail feature flag strategies, canary rollout stages, metrics/SLOs, and rollback triggers.
Agent Safety Guardrails & Anti-Hallucination Rules
- DO NOT author an RFC without analyzing at least two alternative approaches.
- DO NOT omit explicit rollback triggers and non-goals.
Expected Output Format
Publication-ready engineering design document.
Domain Verification Checks
Example Agent Invocations
Install / Configure This Skill
# Place in .cursorrules or create .cursor/rules/technical-design-document-rfc-generation.mdc # Trigger: Whenever you perform technical design document (rfc / adr) generation --- name: technical-design-document-rfc-generation description: Author comprehensive engineering RFCs and Architecture Decision Records (ADRs) with trade-off matrices and rollout plans. version: 1.1.0 compatibility: [Cursor, Claude Code, Cline, Roo Code, Antigravity] --- # Technical Design Document (RFC / ADR) Generation ## Objective Author rigorous, publication-ready technical design documents to align engineering teams on complex architectural initiatives. ## Workflow 1. **Goals & Non-Goals**: Define strict scope boundaries and operational success metrics. 2. **System Design**: Specify component responsibilities, data models, and API contracts. 3. **Trade-offs**: Compare at least two alternatives with a trade-off decision matrix. 4. **Operations**: Detail feature flag rollouts, observability metrics, and rollback criteria.
Need a quick one-time prompt for chat?
Try the Technical Design Document (RFC) Generator — a lightweight version designed for 1-click copying directly into Claude, ChatGPT, or Cursor chat.
SprintKit Workflow Integrations
Complementary tools and checklists to pair with this agent workflow.
Related Agent Skills
Explore related procedural workflows in this discipline.
Monolith Decomposition into DDD Bounded Contexts
Deconstruct monoliths or complex systems into bounded contexts with clear domain events and data ownership.
Backward-Compatible RESTful API Design & OpenAPI Spec
Design or review RESTful API contracts for idempotency, pagination, error models, and non-breaking versioning.