retro — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited retro (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
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.
You are an autonomous retrospective-to-ideation agent. Do NOT ask the user questions. Run the full pipeline below without pausing between phases.
TARGET: $ARGUMENTS
If arguments are provided, use them to scope the retrospective (branch name, date range, feature). If no arguments are provided, analyze the full git history.
============================================================ PHASE 1: DEVELOPMENT RETROSPECTIVE (/recall) ============================================================
PARALLEL EXECUTION: After /recall completes and produces findings, use the Agent tool to run follow-up analyses concurrently.
Follow the instructions defined in the /recall skill exactly.
Produce the full retrospective output: Timeline Reconstruction, Pattern Extraction, Dependency Mapping, and Insight Distillation.
Save the retrospective output to docs/dev-retrospective.md (create the docs/ directory if it doesn't exist).
Key outputs to preserve for Phase 2:
Do NOT stop here. Continue immediately to Phase 2.
============================================================ PHASE 2: FEATURE IDEATION (/new-features) ============================================================
Now follow the instructions defined in the /new-features skill exactly.
Read ALL .md files in the docs/ directory — this includes the docs/dev-retrospective.md you just wrote plus any other markdown files that already existed in the folder.
Extract learnings from every file, synthesize feature ideas, and write the report to docs/NewFeatures-X.md (where X is a 3-word kebab-case theme).
IMPORTANT: Features should directly address the pain points and inefficiencies discovered in the retrospective:
============================================================ SELF-HEALING VALIDATION (max 3 iterations) ============================================================
After completing all phases, validate the combined output:
STOP when:
IF STILL FAILING after 3 iterations:
============================================================ OUTPUT ============================================================
When both phases are complete, print a summary:
Files generated:
docs/dev-retrospective.md — Full development cycle analysisdocs/NewFeatures-[X].md — Feature ideas derived from retrospective learningsKey stats:
Top insight: [single most impactful finding from the retrospective]
Next steps:
/spec [feature name] to generate implementation stories/iterate to start building a feature/research to validate features against competitors============================================================ SELF-EVOLUTION TELEMETRY ============================================================
After producing output, record execution metadata for the /evolve pipeline.
Check if a project memory directory exists:
~/.claude/projects/skill-telemetry.md in that memory directoryEntry format:
### /retro — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.
STRICT RULES:
docs/dev-retrospective.md so Phase 2 can read it.docs/ directory./recall and /new-features apply to their respective phases.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.