What This Skill Does

Procedure

1. Restate the target, the success condition, and any no-touch boundaries before taking action.
2. Inventory what is missing and what context survives: tests, docs, logs, backups, related code.
3. Assess reconstruction feasibility: is there enough context to rebuild accurately?
4. Reconstruct the missing component using the best available evidence.
5. Verify the reconstruction against whatever validation is available: tests, checksums, expected behavior.
6. Mark the reconstruction as reconstructed, not original — provenance matters.
7. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.

Deliverables

• The reconstructed component with a provenance note on what sources informed the reconstruction.
• A confidence assessment: how accurate is the reconstruction and what might be wrong?

Pitfalls / Guardrails

• Keep the metaphor anchored to a real mechanism instead of drifting into lore.
• Clearly mark reconstructed data as reconstructed. Never present regenerated content as if it were the original.
• If there is not enough context for accurate reconstruction, say so rather than generating plausible but potentially wrong content.

Verification

• Check that the result includes every deliverable promised above.
• Check that confirmed facts, assumptions, and inferences are visibly separated.
• Check that the metaphor still maps cleanly to a real operational mechanism.

Example Invocation

/regenerate reconstruct this [lost file/deleted component/corrupted data] from surviving context, tests, and documentation