← ClaudeAtlas

discovery-work-breakdownlisted

Cross-domain / Research methodology and experiment design — Build or re-plan a Microsoft Discovery project's task tree from its Purpose, Outcomes, rubrics, and existing tasks and statuses: one root, a milestone per outcome, and as many leaf tasks as the work needs. Every task at every level gets validation requirements and real dependencies. Suggests an execution pattern per leaf (deterministic, guided, autonomous), inserts human-in-the-loop pause tasks before safety-critical or high-cost steps (autonomous-lab protocols, HPC or cloud runs), and plans cloud compute when the goals need it. Shows the full shape in chat for feedback and approval, then creates it with the tasks tool. USE FOR: 'break down the work', 'plan my tasks', 'build the task tree', 'turn my outcomes into tasks', 're-plan tasks', 'where should a human sign off', 'do we need cloud compute'. DO NOT USE FOR: a standalone investigation design file (use discovery-design-tasks), defining outcomes (use discovery-define-outcomes), or executing tasks.
timothymeyers/discovery-tools · ★ 1 · AI & Automation · score 70
Install: claude install-skill timothymeyers/discovery-tools
# discovery-work-breakdown Turns a project's Purpose and Outcomes into a task tree that Discovery can execute. Every task has validation requirements, every ordering is a real dependency, risky or expensive steps sit behind a human pause, and compute that won't fit on a workstation is planned up front rather than discovered mid-run. ## Hard rules 1. **Never ask with the question modal.** Do not call `askQuestions`. Show the proposed shape in chat, ask any questions as a short numbered list, then end your turn and wait. 2. **Create nothing until the user approves.** Iterate on the shape as many times as they want first. 3. **Validation requirements on every task**: root, milestones, leaves, and pause tasks. The `tasks` tool takes them as `acceptanceCriteria` (an array of strings); Discovery stores them as `validationRequirements`. 4. **Dependencies go on the dependent task, never on a parent.** A parent that depends on its own children stays blocked forever. Order children with `addDependency` between siblings. 5. **Never delete, and never touch work in progress.** Leave tasks that are `complete`, `executionDone`, or `executing` alone. Retire unwanted tasks with `transition status=removed` plus a comment, and only when approved. 6. **Never invent thresholds.** If a rubric or outcome has no number, write `TBD` in the requirement and ask. ## Modes - **Proposal-only** (called by `discovery-project-setup` Step 4): return `## Tasks` ops in that