resource-development

To decompose a contract into work packages, apply this skill after the Sit-Down to organize signed clauses into independent, verifiable tasks. It generates an execution plan that maps work packages to clear territories and allocates token budgets for parallel execution.

An execution plan is a detailed task breakdown that governs contract implementation by mapping work packages to territories and token budgets. You need it after signing a contract and holding a Sit-Down session to establish traceability and coordinate multi-team parallel work safely.

Git isolation works for managing parallel work packages by establishing separate branch workflows for safe execution. The execution plan coordinates these isolated git workflows, ensuring each work package remains independent and verifiable while teams operate concurrently within allocated token budgets.

The best way to allocate token budgets across work packages is by generating an execution plan that maps each contract clause to a specific territory with a defined budget. This ensures parallel execution stays coordinated and traceable to the original contract requirements.

Contract work packages lack traceability during execution when they are not explicitly mapped to signed contract clauses. Generating an execution plan with this skill enforces clause-level traceability, ensuring each independent work package remains verifiable against the original contract terms.