j-mauro-r/SAT-Dengue-V2 / .agents/skills/deepworkplan/create
deepworkplan-create
VerifiedCreate a Deep Work Plan for short or long work. Detect planning intent, materialize a compact Lite proposal first, then retain Lite or expand to Full task files when needed. Supports guided and trust handoff without executing product work.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 54.5 KB |
| addon-augmentations.md | markdown | 4.7 KB |
| orchestrator.md | markdown | 2.7 KB |
| team-agents.md | markdown | 4.6 KB |
| v6.md | markdown | 6.7 KB |
v6.md
View on GitHub# Create — a v6/v7 plan (outcome contract, guarded materialization)
Read this file when creating a plan with the current pack. It covers both
contract generations of the same record layer: **v7 is the default for new
plans on the 7.x pack** (contract `schema` =
`https://deepworkplan.com/schema/plan-contract/v7.json`, the v6 contract
plus the optional `tasks[].parallel_safe` marker; its journal also records
delegation — [`spec/V7_CONTRACT.md`](../spec/V7_CONTRACT.md)); an explicit
`v6` request writes `https://deepworkplan.com/schema/plan-contract/v6.json`
and the v6 rules below apply unchanged. `materialize` derives the manifest
and journal generation from that URL. Existing plans keep their recorded
generation.
A v6 plan is two authored artifacts plus one guarded sequence:
**Plan identity before authoring.** Resolve `dwp_dir` through
`../shared/context.sh`. For v6, convert the requested name to a 2–5-word
lowercase snake_case slug. On a resumed create request, reuse the matching
partial plan only after checking its recorded objective; an ambiguous slug
needs the full folder name or ID. For a new request, claim the next plan folder
exactly once with:
```bash
python3 ../shared/plan_paths.py --plans-dir <dwp_dir>/plans allocate <slug>
```
The helper creates and prints a flat folder such as
`.dwp/plans/PLAN_001_improve_release_docs/`. Its three-digit minimum is
zero-padded; numbers are never reused after a plan is deleted. Use the printed
basename **verbatim** as the plan identifier in markdown, `contract.plan`,
manifest, journal and all later commands. Do not allocate again when resuming
partial materialization: reuse the existing folder. Existing unnumbered plans
stay in place and continue under their recorded lifecycle.
1. **The plan markdown** — `README.md` and task files in the claimed
`.dwp/plans/PLAN_<id>_<name>/`, exactly as in the recorded flow (T-* ids,
one objective per task, `Read Before Starting`, `Acceptance Criteria`
with `AC-*` IDs, and a runnable `Validation` gate).
Acceptance criteria appear in the plan as `AC-*` ids **and** in the
contract verbatim — the markdown is what the approval digests, so edit
it before materializing, never after approval (a changed plan needs a
new digest; that is refine territory). A plan folder with no markdown
is not approvable and `materialize` refuses it.
2. **The outcome contract** — a `contract.json` draft **outside** the plan
folder until materialized (e.g. `.dwp/plans/PLAN_<id>_<name>.contract.json`):
outcome, `acceptance_criteria` (each with evidence class: an executed
gate, a controlled pair, or an asserted human sign-off), `invariants`
with their evaluation boundary, `scope` (allowed command classes,
touched surfaces), `resource_envelope` with per-limit enforcement and
optional reserves, `scheduling`, `permissions`. Authorship guidance and
the closed field set: [`spec/V6_CONTRACT.md`](../spec/V6_CONTRACT.md).
A shipped working shape: [`../examples/V6_PLAN_EXAMPLE.md`](../examples/V6_PLAN_EXAMPLE.md).
Each `gate_intent` `check` is the exact command its gate runs, and its
first word MUST be a declared command class — wrap shell builtins,
`VAR=value` prefixes and compound commands as `bash -c '…'` with
`bash` declared (a check for an asserted-only criterion describes the
human check and is not run). Command classes are an allowlist of entry
points, **not a sandbox**: a shell-run check can chain commands, so the
contract's scope and its review are the control. Validate before proposing: `python3
../shared/contract_v6.py validate-contract <draft.json>` — it refuses
checks the gate runner would refuse and criteria nothing can close
(`--help` lists `--parent` for revisions); `materialize` refuses the same.
3. **Materialization** (guarded, resumable — manifest, then contract, then
approval):
```bash
python3 ../shared/ledger.py --plan <dir> materialize --contract <draft.json> \
[--authority <who>] [--mechanism plan_authorship|pre_authorization] [--note <text>]
```
The helper — never the model's hands — writes `manifest.json` (the
contract pointer that makes the plan's v6-ness discoverable even if the
sequence is interrupted), stamps the content-addressed `contract.json`
into the plan folder, and appends the **first journal event**: the
`approval` citing the contract id and the plan-markdown digest. Only that
event opens the task-start gate; a hand-copied contract without it is
refused at `start` (exit 3), and a manifest whose pointer does not match
the materializing contract is refused rather than rewritten.
`mechanism` is the honest record of how authority was granted:
`plan_authorship` (the human authored or reviewed the plan+contract
before execution) or `pre_authorization` (a standing grant with a stated
envelope — trust mode). Both modes gate identically (A2/A3); what differs
is the recorded authority, never the checks. `--authority` names the
human; an honest name beats a precise one. Authority an agent relays from the
developer says so (`relayed by <agent>`), and the developer's own words are
kept verbatim in a note inside the plan folder — never in scratch space.
**v7: marking `parallel_safe` and granting delegation.** Mark a task
`"parallel_safe": true` only when **all** hold: the repository enables a
delegation addon (`python3 ../shared/config.py enabled --repo <repo>` lists
`agentkit` or `herdr`); the task's touched surface does not overlap a
sibling that could be in progress at the same time; it declares a bounded
output; and its gates run in this plan. Otherwise omit the field — absent
is false, and with no delegation addon the marker is noise. Grant
`agent_delegation` only when the developer accepts delegation for this
plan (trust mode records it as part of the pre-authorization); a marker
without the grant authorizes nothing (`../spec/V7_CONTRACT.md` §2). A
delegation transport may launch delegates with the agent CLI's elevated
permissions: before recording the grant, read the enabled transport
addon's permissions note and tell the developer what it means.
Interrupted materialization (manifest without contract, contract without
approval) → re-run the same command with the same inputs; it resumes and
says so. A **different** contract for a materialized plan is never
written over the old one — that is a revision, the refine amendment path
(`contracts/` chain, fresh approval).
After materialization: report the contract id and the plan digest back,
and route to **execute** (the v6 loop). Never auto-execute; the create
flow ends at the approval event, exactly as in guided mode.
Lite v6: same sequence, a single-task contract with the essential
criteria (the fixtures show the floor). Lite is a representation choice,
not a weaker gate — every criterion still closes only on its evidence
class.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |