What problem does it solve? When repeated local fixes no longer add up to a coherent product, this Skill reconstructs what the system is actually trying to be from documentary, technical, operational, and lived evidence, then turns that understanding into a manifesto that guides future decisions. ## Core Features & Use Cases - Architecture archaeology: Traces original intent, current system boundaries, and lived operator experience across repositories, git history, tests, logs, and conversations, maintaining an evidence ledger labeled observed, claimed, inferred, or undecided. - Manifesto drafting: Produces a governing document with purpose, promise, principles, boundaries, a decision test, and ambition, written to survive changes in language, framework, or repository layout. - Independent review and operator interview: Stress-tests the draft with a peer reviewer and resolves normative questions one at a time with the operator before delivery. - Use Case: A multi-repository product keeps patching the same integration failure in different services. Use this Skill to trace the violated promise across every touchpoint, identify where responsibility drifted, and deliver a manifesto that rules out the wrong designs going forward. ## Quick Start Use the rethink skill to reconstruct this project from evidence and write a governing manifesto before making more local fixes.
