quick

/quick — Fast Path Workflow

Execute a lightweight workflow for trivial changes: $ARGUMENTS

Use for: Documentation fixes, typos, comments, small refactors, non-behavioral changes.

Do NOT use for: New features, behavioral changes, anything requiring RFC/ADR.

WORKFLOW

CRITICAL: Steps MUST be executed in exact order. Do NOT skip ahead. Each step MUST be fully completed before starting the next.

1. Validate Environment

govctl status

Detect VCS: Try jj status first. If it succeeds, use jujutsu. Otherwise use git.

2. Create Work Item

govctl work new --active "<concise-title>"
govctl work add <WI-ID> acceptance_criteria "chore: Change completed"

3. Implement

GATE: Confirm <WI-ID> was created in step 2 before proceeding. Do NOT write any code until the work item exists.

Make the changes. If referencing governance artifacts in code comments, use [[artifact-id]] syntax:

// Implements [[RFC-0001:C-FOO]]

Run validations:

govctl check

4. Record

# jj
jj commit -m "<type>(<scope>): <description>"

# git
git add . && git commit -m "<type>(<scope>): <description>"

5. Complete

govctl work tick <WI-ID> acceptance_criteria "Change completed" -s done
govctl work move <WI-ID> done

6. Final Record

# jj
jj commit -m "chore(work): complete <WI-ID>"

# git
git add . && git commit -m "chore(work): complete <WI-ID>"

WHEN TO SWITCH TO /gov

If during implementation you discover:

• This requires behavioral changes → switch to /gov
• This needs RFC specification → switch to /gov
• This is an architectural decision → switch to /gov

BEGIN EXECUTION NOW.