← ClaudeAtlas

discovery-clarify-projectlisted

Cross-domain / Research methodology and experiment design — Review the current Microsoft Discovery project's purpose, expected outcomes, and task list, then surface up to 5 targeted clarifying questions to the user via `/askQuestion` about ambiguities, gaps, or concerns before any work begins. Goal is to give the user a chance to reconsider scope, assumptions, or approach before kickoff. USE FOR: 'clarify this project', 'ask me clarifying questions before we start', 'review the project and challenge assumptions', 'pre-flight the project plan', 'what's ambiguous about this project'. DO NOT USE FOR: executing tasks, generating a plan from scratch, or reviewing completed work.
timothymeyers/discovery-tools · ★ 1 · AI & Automation · score 70
Install: claude install-skill timothymeyers/discovery-tools
# discovery-clarify-project Pre-flight a Microsoft Discovery project by surfacing clarifying questions **before** any task is executed. This is a lightweight sanity check that gives the user one final opportunity to reconsider scope, assumptions, or approach. ## When to run The user asks you to review, clarify, pre-flight, or challenge the current project before getting started. Typical trigger phrases: - "clarify this project" - "ask me clarifying questions before we begin" - "review the project and flag anything ambiguous" - "any concerns before we start?" ## What to do 1. **Read the project context.** Load the current Discovery project's: - Purpose / problem statement - Expected outcomes / success criteria - Task list (planned steps, deliverables, or subtasks) 2. **Identify ambiguities and concerns.** Look specifically for: - Undefined success criteria or vague outcomes - Missing constraints (time, budget, data access, tools) - Task steps that assume prerequisites not listed in the project - Conflicts between stated purpose and the task list - Scope that appears too large, too small, or off-target - Unstated dependencies on other people, systems, or data - Ambiguous ownership or handoff points 3. **Surface up to 5 questions via `/askQuestion`.** Rules: - **Maximum 5 questions.** Fewer is better if the project is clear. - Each question must be **specific and actionable** — the user should be able to answer it in one or two se