domains / families / software-engineering / resumable-implementation-contracts

resumable-implementation-contracts

authentic

Create repository-based execution contracts for multi-session implementation work, with stable task IDs, evidence, checkpoints, and exact resume state.

When to use

• spans multiple sessions, agents, branches, or context windows;
• has dependencies or acceptance criteria that must survive interruption;
• needs an exact resume point rather than a narrative handoff;
• can appear complete before runtime, artifact, UI, or test evidence exists;
• must preserve partial work and unrelated repository changes.

When not to use

• This structure preserves execution state but cannot resolve unclear product
• Evidence quality depends on running checks that exercise the real behavior;
• Concurrent writers still need repository-level coordination to avoid
• The five-document layout is unnecessary overhead for small, single-session

Skill page

Source