skills.rest
blauwtje
blauwtjeCOMMUNITY
Explore all skills by this author →
GitHub

shaping

Interviews open product decisions and writes a buildable brief before implementation.

1|Updated Sep 10, 2026
Search Tags:#planning#spec writing#claude code#brief#product decisions#requirements interview#decision map
One-click install
npx skills add https://github.com/blauwtje/exo --skill shaping-blauwtje
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shaping
Source: https://github.com/blauwtje/exo/tree/main/skills/shaping
Command: npx skills add https://github.com/blauwtje/exo --skill shaping-blauwtje

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Requests often name an outcome while leaving product decisions open: what counts as done, which data it stores, or which architecture carries it. Coding through those unstated decisions produces work nobody asked for. This skill turns an outcome into a decided brief by asking only the decisions the user would notice, deciding routine ones itself, and recording every answer with who closed it. ## Core Features & Use Cases - Decision map interview: Maps every open product decision, closes the ones the repository already answers with path evidence, and asks the rest in rounds of at most four questions with recommended options. - Two modes: Explore mode compares directions with stated trade-offs when the user asks for options; Specify mode grills, checkpoints, and writes the brief when the user wants the outcome built. - Brief storage: Writes the decided brief to docs/specs/<topic>.md or a GitHub issue marked with an exo:spec header, so a later session resumes from the stored copy after a context clear. - Use Case: A user asks to add a data export feature without saying what format, which records, or where it starts. The skill asks those three decisions in one round, settles file placement from repository conventions, and writes a brief with goal, decisions, acceptance checks, and proof seam. ## Quick Start Ask the AI to shape the outcome you want built, for example by invoking /exo:shaping with a short description of the result you have in mind.

Frequently Asked Questions about shaping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a vague feature request into a buildable spec?▼

Invoke the shaping skill with the outcome you want. It maps every open product decision, closes the ones the code already answers, asks the rest in rounds with recommended options, and writes a brief with goal, decisions, scope, and acceptance checks.

When should I use shaping versus going straight to planning?▼

Use shaping only when the request leaves a product decision open that the user would notice in the finished result. A clear goal with zero open decisions skips the brief entirely and goes directly to planning or implementation.

Where does the shaping skill store the brief?▼

The brief is stored where the exo specs setting says: docs/specs/<topic>.md by default, or a GitHub issue whose body opens with an exo:spec marker when specs is set to issues or both. The location is named in the reply.

Can shaping reopen a brief that already exists?▼

Yes. New wishes for work that already has a brief, issue, or plan reopen that stored brief in place rather than writing a second one. Only decisions the new wishes contradict or leave unanswered go back on the decision map.

What happens if I answer go during the interview?▼

Answering go takes the recommended answer for every decision still open, asked or not, and moves directly to the checkpoint. Those decisions are recorded as closed by exo rather than by you.

Why does shaping refuse to ask some questions?▼

Routine decisions such as names, file placement, and choices with one conventional answer are decided by the skill, never asked. Only decisions the user would notice in the result or that are costly to reverse are asked.

Related Skills

Explore More Product & Management Skills→
aws-samplesaws-samples
186

github

Manage GitHub issues, pull requests, branches, and repository metadata via OAuth.

Official
Intermediate
earchibaldearchibald
70

executing-plans

Execute implementation plans in controlled batches with review checkpoints.

Community
Intermediate
akiotanaka847akiotanaka847
2

debrief-an-interview-loop

Synthesize multi-interviewer feedback into themes, rubric scores, and a recommendation memo.

Community
Advanced
Goblin1024Goblin1024
6

deep-interview

Clarify user intent and non-goals through a structured Socratic interview process.

Community
Intermediate