immutable-spec
Keeps people and AI working from the same spec and linked documents, with every plan, decision, outcome, and piece of validation evidence recorded as the project evolves.
We’ve packaged the methods we use for requirements, design, development, and code review into small, focused skills you can install independently.
Keeps people and AI working from the same spec and linked documents, with every plan, decision, outcome, and piece of validation evidence recorded as the project evolves.
Before implementation starts, check whether the problem is real, the solution is unnecessarily complex, and its key assumptions actually hold.
Define module responsibilities and interactions before writing code, so complexity stays in the right place and the system remains easier to change and test.
Work one behavior at a time: write a failing test first, then add only enough code to make it pass.
Have three isolated reviewers inspect the same changes independently, then verify and merge their findings for a human to decide what to address.
Maintain a concise map of important directories, module responsibilities, and entry points so people and agents can find their way through the codebase quickly.