← ClaudeAtlas

discovery-project-setuplisted

Cross-domain / Research project setup — Set up a new Microsoft Discovery project, or update an existing one from new information, using a propose-then-apply workflow. Covers Purpose, data intake (Bookshelf, local datasets, external sources), Outcomes, task breakdown, and agents / skills / tools / A2A remote agents. Two modes: "propose a full project" (e.g. from an uploaded grant application or proposal) or "walk me through it" step by step. Never deletes; retires via conventions. Keeps a git ledger of every applied change. USE FOR: 'set up my project', 'set up Discovery', 'here is my grant, propose a project', 'start a new project', 'update the project with this new info', 're-plan the project', 'walk me through project setup', 'what's missing from my project setup'. DO NOT USE FOR: executing tasks, grading outcomes, or a single narrow change that a sub-skill handles alone (discovery-define-outcomes, discovery-curate-bookshelf, discovery-provision-tools, discovery-work-breakdown).
timothymeyers/discovery-tools · ★ 1 · AI & Automation · score 70
Install: claude install-skill timothymeyers/discovery-tools
# discovery-project-setup Router for creating or updating a Discovery project. Every change goes through the same loop: **gather current state -> draft desired state -> write proposal -> user approves -> ledger commit (before) -> apply approved ops -> verify -> ledger commit (after)** ## Hard rules 1. **Never mutate Purpose, Outcomes, Tasks, Bookshelf, data/, agents, skills, or MCP config without an approved proposal.** The proposal file is the gate. Apply only ops marked approved. 2. **Never delete.** Tasks -> `removed`; Outcomes -> superseded convention; shelves/sources -> retired convention. See [references/retirement.md](references/retirement.md). 3. **Ask questions as plain chat** — a short numbered list, then end your turn and wait. Do NOT use the askQuestions / question-modal tool. In a non-interactive context (engine, SDK, subagent), write the proposal and stop without applying. 4. **Ledger:** commit before and after every apply. Never push. See [references/git-ledger.md](references/git-ledger.md). 5. **No secrets in tracked files.** Credentials are referenced by env var or Key Vault name only. 6. Scientific content uses LaTeX delimiters (per workspace instructions). ## Step 0 — Detect mode and gather state Read [references/gather-state.md](references/gather-state.md) and build the current-state snapshot. Then classify the request: | Signal | Mode | |---|---| | Empty project + user supplies documents / "propose" | **Full proposal** |