Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Guides structured authoring of engineering RFCs by enforcing a fixed German-language template with mandatory sections. Before drafting, it validates that five input categories are present: problem, stakeholders, constraints, alternatives, and risks. Outputs decision-oriented documents with explicit trade-offs, assumptions, and success criteria.
Enforces intake validation and a non-negotiable heading structure, preventing the common failure mode of publishing RFCs that omit risks, skip non-goals, or bury assumptions.
When to use it
- Writing an architecture decision record for a new service
- Formalizing a database migration proposal for stakeholder review
- Documenting a rejected alternative with rationale for future reference
- Structuring a security or compliance constraint into a team decision doc
- Producing a rollback-aware proposal for a breaking API change
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Write an RFC for switching our authentication system from session cookies to JWTs
- 1Checks that all five required input categories are provided: problem, stakeholders, constraints, alternatives, risks
- 2Asks clarifying questions for any missing categories before proceeding
- 3Drafts the RFC using the exact mandatory heading order: Zusammenfassung, Motivation, Ziele, Nicht-Ziele, Vorschlag, Anhang
- 4Applies decision guardrails: adds decision status and owner in Zusammenfassung, measurable evidence in Motivation, success criteria per goal, alternatives and risks in Anhang
- 5Runs quality gate checks and revises any section that fails before producing final output
A complete RFC document in German-headed sections with decision status, explicit assumptions, trade-off analysis, and open questions assigned to owners