SuperAPI AI Directory

reengineering-vibe-code

Coding & development

View repository

Updated 10-29 14:14

About this skill

Reengineering Vibe Code

Path 2: vibe-reengineering.mmd. Router: vibe-orchestrator-agent.md.

Contents

  • Constraints • Quick start • Workflow • Verification • References

Constraints

  • Truth order: specs/REQS.md > tests/characterization/ > /domain > derived specs > prototype code (rules). A conflict is HUMAN_REQUIRED.
  • Never autonomously rewrite auth, billing, cryptography or compliance logging; they need a hash-bound human-approval.json.
  • Characterization tests assert legacy behavior verbatim; fixtures contain no absolute paths or secrets.
  • Only the four independent agents decide: domain-purity-auditor, semantic-drift-auditor, certification-verifier (sole authority for slice-certified) and business-rule-audit-agent. After two rejections for the same issue, escalate to the user.
  • Do destructive work in an isolated workspace (os-control-worktree skill). Register the task through os-control-intake only when the user runs a control plane.
  • Ask the five architecture questions one at a time. Pick runtime and model through the cli-agent skill.

Quick start

test -f exploration/captures/DISCOVERY_REPORT.md || echo "start at phase 1"
ls specs/REQS.md tests/characterization 2>/dev/null

Workflow

Seven phases (guide): browser audit, safety net, five questions, REQS and risk gate (full architecture package optional), domain extraction with purity audit, target scaffolding (ADR, ports, session memory), slice migration with drift audit and certification. Finish by handing to handing-off-to-engineering.

Verification

Run the characterization suite (100 percent parity), the purity and drift reports, and the certification report in temp/.

Acceptance criteria: acceptance-criteria.md.

References