draft-execution-contractlisted
Install: claude install-skill kotnisofiane-bit/dubsar-agent-skills
# Draft Execution Contract
## Objective
Translate one candidate lot into an explicit, reviewable local work agreement.
## Inputs
- the approved `mission.json`;
- `lots.json` with exactly one `candidate` lot;
- known targets, protected areas, validation methods, evidence requirements,
recovery expectations, and authority constraints.
## Workflow
1. Select exactly one `candidate` lot.
2. Resolve its concrete target paths or systems.
3. List allowed actions narrowly. Keep read-only inspection separate from
mutation.
4. List forbidden actions and protected areas.
5. Record validation commands or observable checks.
6. Define the evidence files that must exist at completion.
7. Record rollback or recovery expectations for each material mutation.
8. Add stop conditions for ambiguity, unexpected changes, failing validation,
or missing authority.
9. Ask for approval before execution begins.
## Output
Write `execution-contract.json`:
```json
{
"format": "dubsar.execution-contract/1",
"mission_id": "same-as-mission",
"lot_id": "selected-lot",
"contract_id": "local-stable-id",
"targets": [],
"allowed_actions": [],
"forbidden_actions": [],
"protected_areas": [],
"validation": [],
"required_evidence": [],
"recovery_expectations": [],
"stop_conditions": [],
"status": "draft"
}
```
## Limits
- Keep the contract in `draft` state until the user approves it.
- Do not invent unresolved targets, permissions, validation, or recovery steps.
- Do not exec