swingerman/simplify
engineer/skills/simplify/SKILL.md
Use after a feature's code is implemented and passing, to clean up the changed code before verification. Triggers — "/engineer.simplify", "simplify this code", "clean up the feature", "refactor what we built".
$ install --global
skillsauthnpx skillsauth add swingerman/atdd simplifyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 17, 2026, 4:27 AM111.7s1 file scanned
SKILL.md
- name:
- simplify
- description:
- Use after a feature's code is implemented and passing, to clean up the changed code before verification. Triggers — "/engineer.simplify", "simplify this code", "clean up the feature", "refactor what we built".
simplify
Charter-bound clean-up of a feature's changed code — Checkpoint 6. Modeled on Claude Code's stock /simplify (a three-subagent parallel review) with two layers the stock skill lacks: charter validation of every proposal, and graceful breaking changes.
The behavior contract (ACs + specs) is sacred — a refactor that breaks it is a category error. New shapes are introduced alongside old, never instead of.
When to use
Checkpoint 6, after atdd:atdd-team produces passing code, before crap-analyzer (Checkpoint 7).
Verification independence: if manifest.verification.apply_to_checkpoints includes 6, simplify must run on a non-implementer agent. The three review subagents (Step 2) are fresh regardless, so independence is satisfied by construction.
Not for: changing behavior (feature-edit); risk analysis (crap-analyzer); code that isn't implemented/green yet.
Workflow
- Resolve + scope — resolve the methodology root + manifest via
${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py(seereferences/resolving.md); locate the feature. Scope = the feature branch's changed code (git diffagainst the branch point). Loadfeature.md,acs.md,spec.md,CHARTER.md. - Dispatch three parallel review subagents (
superpowers:dispatching-parallel-agents), each over the same changed code:- Reuse — duplication, reinvented wheels, dead code, missed existing utilities
- Quality — clarity, structure, naming, incidental complexity, maintainability
- Efficiency — redundant computation, repeated lookups, visible performance smells
- Consolidate — merge findings; dedup overlaps (note multi-lens hits as strong signals); keep genuine conflicts as alternatives for the human.
- Charter filter — check every proposal against
CHARTER.md(architecture, conventions, methodology, the ACs+specs contract). Charter-violating proposals are rejected internally — never shown. This filter is the DAE-specific layer the stock skill lacks. - Classify breaking changes — consumer-facing (something outside the blast radius depends on the old shape) → graceful path: deprecation-marked forwarding shim + migration note, new shape alongside old. Internal-only → hard change is fine.
- Present; human picks — show charter-compliant proposals (change, why, blast radius, churn). The human selects which are worth the churn.
- Apply — apply selected; install graceful paths where needed; re-run both test streams. Any failure → revert that proposal and report.
- Handoff — emit a summary.
If a charter rule itself blocks a genuinely better design, surface it in the handoff (→ feature-edit / charter amendment). simplify does not amend the charter.
Handoff
Emit per ${CLAUDE_PLUGIN_ROOT}/references/handoff-summary.md. agent_id must differ from the implementer if checkpoint 6 is independence-gated. checkpoint: 6; recommended_next: "crap-analyzer for Light Verify".
References
superpowers:dispatching-parallel-agents— the Step 2 dispatch pattern- Foundation Design — charter format, verification independence
Related Skills
swingerman/post-merge
data-ai
VerifiedTrustedCommunity
Use immediately after a PR is merged to clean up the local feature branch and resync main. Triggers — "/engineer.post-merge", "did we merge", "did we push", "PR merged", "post-merge cleanup", or right after a `gh pr merge` succeeds in the same session.
103SKILL.mdUpdated Jun 5, 2026
swingerman/fix
data-ai
VerifiedTrustedCommunity
Use to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end. Triggers — "/engineer.fix", "a bug came in", "this is broken", "a user reported X", "there's a defect", "we have a regression", "this needs a fix", "another report", "more issues", "still failing", "validation failed again", "another bug", "next defect", "more fixes".
103SKILL.mdUpdated May 26, 2026
swingerman/reorient
testing
VerifiedTrustedCommunity
Use mid-task when the working thread is lost — after a context compaction, a long agent run, or coming back to a feature unsure of the role, the current checkpoint, or the next action. Triggers — "/engineer.reorient", "reorient", "re-anchor", "what should I be doing right now", "I lost track", "where was I".
103SKILL.mdUpdated May 20, 2026
swingerman/arch-check
development
VerifiedTrustedCommunity
Use to check a feature's code against the charter's architecture rules — dependency layering, cycles, forbidden patterns, file naming, file size. Triggers — "/engineer.arch-check", "architecture check", "check architecture fitness", "does this follow the charter", "check layering".
103SKILL.mdUpdated May 19, 2026