Skip to content

j-mauro-r/SAT-Dengue-V2 / .agents/skills/deepworkplan/create

deepworkplan-create

Verified

Create 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.

FileKindSize
SKILL.mdskill md54.5 KB
addon-augmentations.mdmarkdown4.7 KB
orchestrator.mdmarkdown2.7 KB
team-agents.mdmarkdown4.6 KB
v6.mdmarkdown6.7 KB

orchestrator.md

View on GitHub
# DeepWorkPlan — Create: orchestrator branch (read only when Step 2.6 fires)

This file is read **only** when the `create` flow detects an orchestrator plan
(`SKILL.md` Step 2.6). It carries the orchestrator-specific gathering steps and
the additions to materialization, verbatim from the main procedure. Everything
else (requirements analysis, task anatomy, quality check) is in `SKILL.md`.

## Gathering — orchestrator detection and questions

**2.6 Orchestrator detection (automatic).** After 2.3–2.4, auto-detect an
**orchestrator plan** when: the work spans 2+ sub-repositories with independent
feature work, or the user explicitly mentions child DWPs / orchestrator /
"create plans in each repo". If detected, offer the choice between an
**orchestrator plan** (creates child DWPs per repo, each following its own
`AGENTS.md`) and a **direct multi-project plan**. See `../guide/orchestrator.md` §13 and
`../shared/adaptation.md` (orchestrator-hub archetype).

**2.7–2.9 (orchestrator only):** ask for target repositories (note each repo
root — for an orchestrator hub this is `repositories/{repo}/`), dependency order,
and execution mode (Distributed / Sequential with Output Handoff / Sequential
basic). Default to Distributed. When the developer wants the children run by
lanes — one agent per repository in its own Herdr pane, on chosen accounts —
record the lane table and the release order from
`../guide/orchestration-at-scale.md` §16 in the README.

## Materialization — orchestrator additions

**Orchestrator additions (orchestrator plans):**
- README **Child DWP Plans** table (`# | Repository | Child Plan | Status |
  Depends On`), an **Execution Mode** subsection, and **Dependency Rules**.
- **ORCHESTRATOR_MANIFEST.md** at `.dwp/plans/{PLAN_NAME}/ORCHESTRATOR_MANIFEST.md`
  (template in `../guide/orchestrator.md` §13.8): Shared Context, Child DWP Registry,
  Dependency Graph, Output Contracts, Execution State.
- Task files: direct design tasks first (if hybrid); then `create_child_dwp`
  tasks in dependency order (template
  `../examples/ORCHESTRATOR_TASK_TEMPLATE_create_child_dwp.md`); optional
  `integration_checkpoint` tasks
  (`../examples/ORCHESTRATOR_TASK_TEMPLATE_integration_checkpoint.md`);
  `execute_child_dwp` tasks for Sequential-with-Output-Handoff mode
  (`../examples/ORCHESTRATOR_TASK_TEMPLATE_execute_child_dwp.md`); then the
  Final Review last (`{N}.task_final_review.md`). Each `create_child_dwp` task instructs the agent to
  navigate to the target repo, read its `AGENTS.md`, and allocate a child DWP
  folder under `repositories/{repo}/.dwp/plans/` using that repo's local next
  ID. Record its allocated basename in the parent registry and all references;
  never guess a child ID from the parent plan's sequence.
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall
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: 108kUpdated Claude CodeCodexVerifiedInstall
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: 108kUpdated Claude CodeCodexVerifiedInstall