workflow-reflection-b08133 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited workflow-reflection-b08133 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Execute the reflection and finalization stage. $ARGUMENTS
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.
Before starting, verify:
.workflow/state.json exists and currentStage is "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]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.
Based on the workflow outcome:
If hypotheses were validated (happy path):
# Historical: ADRs archived — update spec status in frontmatter instead of mv .adr/<NNN>-<name>-adr.md .adr/accepted/<NNN>-<name>.md # Historical: ADRs archived — update spec status in frontmatter instead of mv .adr/<NNN>-<name>-summary-*.md .adr/accepted/specs/specs/ or docs/decisions/archive/adr/accepted/ are now outdated by this work, update themIf hypotheses were refuted:
# Historical: ADRs archived — update spec status in frontmatter instead of mv .adr/<NNN>-<name>-adr.md .adr/rejected/<NNN>-<name>.mdIf the workflow was abandoned or partially completed:
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" git fetch origin
git rebase origin/mainIf conflicts arise, resolve them or escalate to user.
git push -u origin <branch> Branch is pushed and PR is ready.
Merge now, or leave open for review?Invoke /capture-learning to extract reusable learnings from this workflow session. Pass it the reflection from Step 1 as context.
Set the final state:
{
"stages": {
"reflection": {
"status": "completed",
"completedAt": "<ISO timestamp>"
}
},
"currentStage": "completed",
"updatedAt": "<ISO timestamp>"
}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">~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.