From task
to handoff.

A practical way to combine this collection’s skills without loading every procedure into every task.

This is a suggested workflow, not a claim of benchmarked performance. Each step links to instructions maintained in this repository.

1. Bound the work

Use Work Packet Planner to establish the outcome, owned paths, dependencies, acceptance criteria, and handoff. Resolve shared ownership before parallel work starts.

2. Make the behavior observable

Use Behavior Test Design when behavior is changing. Define the cases and expected outcomes before treating the implementation as correct. Reuse project-owned test infrastructure.

3. Investigate only when needed

When a concrete failure blocks the task, use Evidence First Debugging. Keep the original reproduction, test explanations, and repair the supported cause. Do not turn every edit into an incident investigation.

4. Verify the changed boundary

Use Affected Verification for relevant checks. For a rendered interface, add Interface Quality Review and exercise the actual journey. Mark unavailable checks as blocked or untested.

5. Hand back evidence

Use Worktree Handoff to connect the final revision, changes, check results, unresolved work, and resource ownership. Review the combined integration candidate; isolated success is not integration evidence.

Keep the workflow proportional

A small documentation correction may need none of these extended procedures. Select the skill that solves the current problem rather than impose an entire framework. No skill grants additional tool permissions or approval to publish.