workflow-reflection
SkillDev toolsFinalize the workflow by reflecting on the process, moving ADRs, closing issues, and preparing for merge. Stage 8 of the development workflow.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the workflow-reflection skill
What this skill tells your AI
The instructions your AI receives, as published by kastalien-research/thoughtbox in .agents/skills/workflow-reflection/SKILL.md and read by ahel’s review.
Execute the reflection and finalization stage. $ARGUMENTS
Purpose
You are executing Stage 8 (Reflection) of the development workflow. The implementation is reviewed, revised, and compounded. Your job is to finalize: reflect on what happened, move artifacts to their permanent locations, close tracking issues, and prepare the branch for merge.
Pre-Conditions
Before starting, verify:
.workflow/state.jsonexists andcurrentStageis"reflection"- Stages 1-7 are all completed or skipped (check state file)
- All sub-agent work has been committed (no uncommitted implementation changes)
Process
Step 1: Agent Structured Reflection
Review the entire workflow by reading the state file and any persisted summaries. Produce a structured reflection:
WORKFLOW REFLECTION
====================
Workflow: <id> - <title>
Branch: <branch>
Duration: <startedAt> to now
## What Worked
- [specific things that went well, with evidence]
- [approaches that should be repeated]
## What Didn't Work
- [specific things that went poorly, with evidence]
- [approaches to avoid in future]
## Hypothesis Outcomes
- H1 "<text>": VALIDATED / REFUTED / INCONCLUSIVE
- H2 "<text>": ...
## Revision Iterations
- Total: N/3
- Root causes of revision: [what triggered each iteration]
## Unexpected Discoveries
- [things learned that weren't part of the original plan]
- [codebase behaviors that surprised us]
## Process Improvements
- [suggestions for improving the workflow itself]
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):
- Move the spec with frontmatter to accepted:
# Historical: ADRs archived — update spec status in frontmatter instead of mv .adr/<NNN>-<name>-adr.md .adr/accepted/<NNN>-<name>.md - Move associated summaries with it:
# Historical: ADRs archived — update spec status in frontmatter instead of mv .adr/<NNN>-<name>-summary-*.md .adr/accepted/ - If the spec was in staging, move it to
specs/ - If any existing docs in
specs/ordocs/decisions/archive/adr/accepted/are now outdated by this work, update them
If hypotheses were refuted:
- Move the spec with frontmatter to rejected:
# Historical: ADRs archived — update spec status in frontmatter instead of mv .adr/<NNN>-<name>-adr.md .adr/rejected/<NNN>-<name>.md - Preserve test insights alongside the rejected ADR
- Add rejection reason and falsified hypotheses to the ADR file
If the workflow was abandoned or partially completed:
- Leave artifacts in staging with a note about the incomplete state
- The next workflow that touches this domain will find them during ideation
Step 4: Prepare for Merge
-
Ensure all changes are committed:
git statusIf 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" -
Rebase onto main:
git fetch origin git rebase origin/mainIf conflicts arise, resolve them or escalate to user.
-
Push the branch:
git push -u origin <branch> -
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
-
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>
Spec: <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
Signals
- GitHub stars
- 64
- Forks
- 20
- Last commit
- Jul 2026
Advanced
- Catalog kind
- skill
- Gateway key
workflow-reflection- Source
- github.com/kastalien-research/thoughtbox