shape
/shape
Guides users from a rough project, product, or feature idea to a concise Product Charter by clarifying the audience, problem, solution, boundaries, and success measure. Use when shaping or scoping a new idea.
- Author
- YnotnaUK ↗
- Repository
- ai-skills ↗
- Licence
- MPL-2.0
- Last repository change
- 04.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.
MPL-2.0, otwarta.
What it does and when to use it
Guides users from a rough project, product, or feature idea to a concise Product Charter by clarifying the audience, problem, solution, boundaries, and success measure. Use when shaping or scoping a new idea.
Original author description
Guides users from a rough project, product, or feature idea to a concise Product Charter by clarifying the audience, problem, solution, boundaries, and success measure. Use when shaping or scoping a new idea.
How it works
- Conversation rules
- Workflow
- Closure and shared understanding
- Opening
SKILL.md preview
--- name: shape description: Guides users from a rough project, product, or feature idea to a concise Product Charter by clarifying the audience, problem, solution, boundaries, and success measure. Use when shaping or scoping a new idea. --- # Shape an idea into a Product Charter Help the user turn an early idea into a clear, high-level Product Charter through a short, guided conversation. ## Conversation rules * Ask exactly one clear question per turn. Do not combine questions or ask the user to make several decisions at once. * Use plain, conversational language. Avoid technical and project-management jargon. * If a response is long, winding, or unclear, first reflect its main point in one sentence of 15 words or fewer. Then ask one focused question to confirm or clarify it. * Reuse information the user has already given; do not ask them to repeat it. * Do not invent answers or treat assumptions as decisions. If the user is unsure, help them explore with one simple prompt at a time. * Keep each exchange concise. Offer an example only when it would help the user answer. * Track each relevant question and follow-up branch with a stable identifier and its parent where applicable. Record its answer or decision and supporting evidence. Partial, ambiguous, skipped, or contradictory answers stay open; ask the missing follow-up rather than treating a reply as closure. ## Workflow Work through these gates in order. A gate is complete when its answer is clear enough to state in the charter. Ask only for information that is still missing or ambiguous. 1. **Audience and problem:** Establish who the idea is for, then clarify the main frustration or need. Ask about these separately. 2. **Solution:** Understand the central experience or change that would address the problem from the user's perspective. 3. **Boundaries:** Identify at least two must-haves and one explicit out-of-scope item. Ask for each separately; do not fill gaps with assumptions. 4. **Success:** Define one observable result that would show the idea is working. ## Closure and shared understanding Before delivery, check every gate and tracked branch, including follow-ups opened by earlier answers. Each must be **Resolved**, **Excluded**, or **Deferred**; an unanswered question remains **Open**. Exclusions require the user's agreement. Deferrals require the user's agreement, a reason, a next step, and what they block. Do not defer information needed to complete the four gates. Give a concise recap with the branch outcomes, evidence or decisions, agreed boundaries, and any deferrals and blockers. Ask one question confirming the shared understanding and readiness for `discovery`, then wait. Silence, a partial reply, or acceptance of individual answers is not confirmation of the whole recap. Incorporate corrections, revisit affected branches, and confirm again if the understanding changes. Do not reopen unaffected settled decisions or invent unrelated branches. Do not present the finished charter until all four gates are clear and the user confirms the recap. Then read [the Product Charter template](./references/product-charter.md) and use it to deliver the charter so the user can carry it into the `discovery` skill. Carry the closure record into the charter; do not imply that deferred discovery work is resolved. Before delivery, follow any repository artefact policy and output path in the active repository's root agent instructions. If no clear policy is present, return the charter in chat and do not create or update files unless asked. ## Opening If the user has not already shared an idea, start with: “Hey there! Let’s shape your idea into a clear concept. What rough idea would you like to explore?”
Files in this package (2)
- SKILL.md 4 KB
- references/product-charter.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · YnotnaUK/ai-skills | 100 | MPL-2.0 |
| biliboss/skills | 100 | MIT |
| gmdkaio/kstack | 100 | MIT |
| ebullient/qrspi-x | 100 | Apache-2.0 |
| jamesm-dev/payday-dev | 100 | MIT |
| nyelonong/galdr | 100 | MIT |
| thecraighewitt/skills | 100 | MIT |
| tiago-peixoto/claude-shapeup | 95 | MIT |
| educlopez/ui-craft | 92 | MIT |
Database snapshot: 13.11.2026 · package version c733a6bfadcd (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100feature-design
Use when the user has a rough idea for a feature, product change, or new capability and wants to brainstorm, shape, design, or spec it before building, such as "I'm thinking of adding…", "how should we approach…", "help me design…", or "write a spec for…". - 90idea-calibrate
Turn a raw idea into a calibrated, testable v1 plan before any code. Use when you have only an idea, a rough brief, or a feature request, and need the problem, user, success criteria, assumptions, and non-goals confirmed. Only invoke via the orcinus router. - 100product-shaping
Three-phase product shaping: frame the problem, research it, and shape the solution into a validated spec, then hand off to product-doc for the writeup. Use when scoping a new product investment, turning a vague idea into a concrete opportunity, gathering evidence for a product… - 90brainstorm
Turns no idea or a rough idea into a written product brief: problem, target user, solution, why now, differentiation and riskiest assumption. Use when the user has no idea yet ('open'), a vague idea, or wants to explore directions before writing a PRD. - 90writing-product-specs
Use when asked to write a product spec, PRD, or requirements document, or to design a new feature or project before implementation - interactively elicits problem, audience, success criteria, and scope, then produces a structured spec file - 90wizard
Use when the user has a rough feature, behavior change, improvement, project, or exploration idea and wants to be guided to a clear, agreed approach before planning or implementing, or wants to start a new project or expand a project's scope without yet knowing what to build.