Workflow Reflection

Step 2: User Reflection (Optional)

Ask the user if they want to add their own reflection:

Would you like to add your own reflection notes?
This is optional but valuable for the compound learning record.

If the user provides input, append it to the reflection under a ## Chief Agentic Notes section.

Step 3: Move ADR to Permanent Location

Based on the workflow outcome:

If hypotheses were validated (happy path):

1. Move the staging ADR to accepted:

   mv .adr/staging/<NNN>-<name>-adr.md .adr/accepted/<NNN>-<name>.md
   

2. Move associated summaries with it:

   mv .adr/staging/<NNN>-<name>-summary-*.md .adr/accepted/
   

3. If the spec was in staging, move it to specs/
4. If any existing docs in specs/ or .adr/accepted/ are now outdated by this work, update them

If hypotheses were refuted:

1. Move the staging ADR to rejected:

   mv .adr/staging/<NNN>-<name>-adr.md .adr/rejected/<NNN>-<name>.md
   

2. Preserve test insights alongside the rejected ADR
3. Add rejection reason and falsified hypotheses to the ADR file

If the workflow was abandoned or partially completed:

1. Leave artifacts in staging with a note about the incomplete state
2. The next workflow that touches this domain will find them during ideation

Step 4: Prepare for Merge

1. Ensure all changes are committed:

   git status
   

   If there are uncommitted changes (reflection artifacts, ADR moves), commit them:

   git add <specific files>
   git commit -m "docs: finalize workflow <id> - move ADR, close issues"
   

2. Rebase onto main:

   git fetch origin
   git rebase origin/main
   

   If conflicts arise, resolve them or escalate to user.

3. Push the branch:

   git push -u origin <branch>
   

4. Create or update the PR:

   • If no PR exists, create one
   • If a PR exists, ensure it's up to date
   • The PR description should reference the ADR and include the reflection summary

5. Merge decision: Ask the user whether to merge now or leave the PR open for additional review:

   Branch is pushed and PR is ready.
   Merge now, or leave open for review?
   

Step 5: Delegate Learning Capture

Invoke /capture-learning to extract reusable learnings from this workflow session. Pass it the reflection from Step 1 as context.

Step 6: Update Workflow State

Set the final state:

{
  "stages": {
    "reflection": {
      "status": "completed",
      "completedAt": "<ISO timestamp>"
    }
  },
  "currentStage": "completed",
  "updatedAt": "<ISO timestamp>"
}

Step 7: Final Report

Present the completion summary:

WORKFLOW COMPLETE
==================

<title>
Branch: <branch>
ADR: <final location>

Stages:
  1. Ideation     [x] <notes excerpt>
  2. Dev-Docs     [x] spec: <path>, adr: <path>
  3. Planning     [x] plan: <path>
  4. Implementation [x] commits: N, summaries: N
  5. Review       [x] findings: N (all resolved)
  6. Revision     [x] iterations: N/3
  7. Compound     [x] learning captured
  8. Reflection   [x] ADR accepted/rejected

PR: <url or "merged">

Anti-Patterns

• Do NOT skip the ADR move — artifacts left in staging rot and confuse future workflows
• Do NOT merge without pushing first — local-only merges are invisible to the team
• Do NOT skip the learning capture — the whole point of reflection is to compound
• Do NOT fabricate reflection — base it on actual evidence from the workflow state and summaries