quantumquirkxyz Contract
- Input: problem description and inputs defined by the skill body.
- Output: Markdown artifact with completed process steps.
- Side effects: none.
- Dependencies: none.
- Stop condition: all process steps executed; artifact saved with required sections.
- Risk: low.
- Boundary: produces reasoning artifact only; no system changes.
ADR Creation
Create an Architecture Decision Record (context, decision, consequences, alternatives, status) with an explicit review cycle.
When to use
- A significant architecture choice is made.
- The team needs a durable explanation of design.
- A decision needs to be revisited over time.
Process
- Title, number, date.
- Status — proposed / accepted / deprecated / superseded.
- Context — driving forces, constraints, alternatives considered briefly.
- Decision — positive statement of what was chosen.
- Consequences — positive, negative, neutral; risks and trade-offs.
- Alternatives — listed with brief evaluation.
- Links — related ADRs, PRs, docs.
- Review — set a review date; document why it might be superseded.
- Deliver — Markdown artifact in docs/adr/ directory with the full template.