$npx -y skills add devnomad-byte/cosmosmith --skill cosmosmith-product-discoveryTurn a rough product idea, vague user desire, or early "create a world" concept into a concise Cosmosmith idea brief. Use when the user has not yet provided a clear problem, target user, first valuable slice, or acceptance criteria; may use web research when market context is cur
| 1 | # Cosmosmith Product Discovery |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | Clarify a rough idea without over-questioning the user, then produce `docs/cosmosmith/idea-brief.md`. |
| 6 | |
| 7 | ## Workflow |
| 8 | |
| 9 | 1. Read project `AGENTS.md` if present, `task.md` if present, and any existing `docs/cosmosmith/idea-brief.md`. |
| 10 | 2. Capture the user's seed idea in one or two sentences. |
| 11 | 3. Ask at most three high-leverage Socratic questions only when the answer would change the brief. |
| 12 | 4. Use web research if current competitors, pricing, regulations, or ecosystem expectations matter. |
| 13 | 5. Write or update `docs/cosmosmith/idea-brief.md` using the idea brief structure from the plugin template. |
| 14 | 6. Update `task.md` with the next claimable task for `cosmosmith-spec-governor`. |
| 15 | |
| 16 | ## Output Requirements |
| 17 | |
| 18 | The idea brief must include: |
| 19 | |
| 20 | - User seed. |
| 21 | - Primary user. |
| 22 | - Job to be done. |
| 23 | - Pain or desire. |
| 24 | - Proposed world. |
| 25 | - First valuable slice. |
| 26 | - Acceptance criteria. |
| 27 | - Open questions. |
| 28 | |
| 29 | ## Completion |
| 30 | |
| 31 | Stop when the idea brief is concrete enough for proposal and design work. If the user's intent is still too unclear, mark the task `blocked` in `task.md` with the exact missing decision. |