Loading...
Loading...
Found 4 Skills
Use when you need to produce a D2 decision document (RFC/Decision Doc) for a Spec Pack, and need to independently decide whether to execute D0 (bypass design via diversion) and D1 (optional research) even under pressure, avoiding guessing FEATURE_DIR, making up input details, writing design as implementation specifics, or leaving behind TODO/To-Confirm lists.
Use this skill when writing, reviewing, or improving internal engineering documents - RFCs, design docs, post-mortems, runbooks, and knowledge base articles. Triggers on drafting a design proposal, writing an RFC, creating a post-mortem after an incident, building an operational runbook, organizing team knowledge, or improving existing documentation for clarity and completeness.
Draft a technical Request for Comments (RFC) or technical proposal document based on a rough idea or scattered requirements. Triggers when the user asks to write an RFC, draft a technical proposal, or structure an architecture design.
Create well-structured RFCs and technical proposals for software projects. Use this skill whenever the user wants to write an RFC, technical proposal, design doc, architecture doc, or system design overview. Also trigger when the user says things like "write an RFC", "I need to propose a new system", "create a technical proposal", "document the architecture", "write up the design", "I need a design doc", or "explain the system architecture in a doc". Even if they just say "RFC", "design doc", or "arch doc", use this skill. Covers both RFCs (proposing what to build) and architecture docs (documenting an existing codebase).