Workshop a rough idea into a project brief through guided conversation. Use when the user has an unrefined concept, a spark, or a fragment they want to develop into something concrete — runs a two-phase Q&A (open exploration → targeted resolution) and produces a brief in docs/briefs/. Takes priority over create-project and create-investigation when the idea isn't yet refined enough for those. Triggers when user says "I have an idea", "workshop this", "let's explore a concept", "develop this fragment", "I want to build something new", "let me tell you about this idea", or describes something unstructured that needs shaping.
From project-docsnpx claudepluginhub ichabodcole/project-docs-scaffold-template --plugin project-docsThis skill uses the workspace's default tool permissions.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Retrieves current documentation, API references, and code examples for libraries, frameworks, SDKs, CLIs, and services via Context7 CLI. Ideal for API syntax, configs, migrations, and setup queries.
Uses ctx7 CLI to fetch current library docs, manage AI coding skills (install/search/generate), and configure Context7 MCP for AI editors.
Develop a rough idea into a concrete project brief through guided conversation.
This skill sits at the very beginning of the documentation lifecycle — before investigations, before proposals, before projects. Use it when:
Key indicators:
Not the right skill when:
create-projectcreate-investigationYour goal is to understand the full shape of the idea. Don't impose structure yet. Listen, reflect, and follow the user's energy.
How to approach this phase:
Guidelines:
You'll know this phase is complete when you can articulate:
Now shift to specific questions that fill gaps in the brief. The goal is to reach enough clarity to write the document.
Types of questions to ask:
Guidelines:
You'll know this phase is complete when you can fill every section of the brief template with concrete content (not placeholders).
Before writing anything, present your understanding back to the user:
"Here's what I think this is..."
Cover: the vision, core use cases, what makes it interesting, and what it is/isn't. Get explicit confirmation before proceeding to write.
docs/briefs/YYYY-MM-DD-<name>.md using the template
at docs/briefs/TEMPLATES/BRIEF.template.md as scaffolding.Based on what emerged, suggest specific next steps with rationale. Common paths:
create-project."Offer to kick off the first next step immediately.