agentleFS
Sign inStart free
finolabsfinolabs/vibecode/skills/shape/SKILL.md

shape

Skill4 starsChanged 14 days agoMITView on GitHub

Interview the user in short rounds that settle every decision an idea, plan or design depends on, each question with a recommended answer, before anything is built. Use when the user wants to brainstorm, discuss, ideate, shape or stress-test an idea, plan or design, asks to be grilled or interviewed about it, or when requirements are unclear before building; it fires on these requests in any language the user writes.

37 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use layout, explore and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • owshq-mecSkill

    layout

    Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.

    Also in 8 projects that use this

  • genomewalkerSkill

    explore

    RLM-style recursive memory exploration - dynamically navigate the memory graph

    Also in 3 projects that use this

  • Microsoft AzureSkill

    build

    Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.

    Also in 5 projects that use this

  • AnthropicSkill

    brief

    Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.

    Also in 3 projects that use this

  • jaydubya818Skill

    why

    Use when design rationale must be recovered from source history and available records.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 7 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 35 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Close: When no open decision remains, summarize what was decided and ask the user to confirm it.

    line 33
  2. Distinctive:

    When the user only wants many raw ideas, the first round offers two or three distinct directions as options.

    line 35
  3. Very specific:

    Write each settled decision with its date where the work keeps its decisions: the work record's goal and acceptance section when …

    line 41

“Common” is measured: kept by at least 6 in 10 of the 35 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Shape

Turns an open idea, plan or design into decisions the user has made, one round of questions at a time, and acts on none of it until the user confirms the result.

Learned from grilling by Matt Pocock (mattpocock/skills, MIT); no text is copied.

Topic: $ARGUMENTS

Which interview runs

Advisory (agent judgment), owner's order (12/11/2026):

  1. This skill runs first.
  2. grilling (/grill-me, or /grill-with-docs when the user wants a glossary and decision records kept) runs when this skill is not installed or the user asks for it by name; put its questions through the host's native question tool too.
  3. Superpowers brainstorming only when the user wants many divergent design ideas rather than decisions, and it is installed.

In a Spec Kit repository this skill works inside a phase like the other phase tools and yields to Spec Kit's own clarify step. At router depth MIN, skip it unless the user asked for it.

Procedure

Advisory (agent judgment); no hook or script enforces these steps.

  1. Map the decisions. List what must be decided and draw the dependencies as a tree: a decision is open to ask only when every decision it depends on is settled.
  2. Split facts from decisions. A fact the agent can find (a file, a command's output, a read-only subagent's search) is the agent's to find; never ask the user for it. Choices, priorities and trade-offs are the user's.
  3. Ask one round, in the native form. Ask every open decision whose prerequisites are settled, and nothing that depends on an answer still missing. Each decision is one question in the host's native question tool (AskUserQuestion on Claude Code, request_user_input on Codex, ask_question on Antigravity), never a numbered text list: two to four options, your recommended option first with its trade-off in the option's description, the alternatives after it. A round larger than one call allows (four questions on Claude Code) is split across calls, blocking questions first. Plain text only when the session has no such tool, the tool fails, or the answer is free text. A question that waits on a lookup still running waits; ask the rest now.
  4. Update the tree. Record each answer, add the decisions it opens, drop the ones it closes, and ask the next round.
  5. Close. When no open decision remains, summarize what was decided and ask the user to confirm it. Act on nothing (no code, no file, no dispatch) before that confirmation.

When the user only wants many raw ideas, the first round offers two or three distinct directions as options; later rounds go deeper on the one they pick.

Records

Advisory (agent judgment):

  • Write each settled decision with its date where the work keeps its decisions: the work record's goal and acceptance section when coding-router created a work record, otherwise the plan, the issue or the pull request body.
  • A decision the user cannot make yet stays open in that record, with who owns it and what would unblock it.
  • In a delegated or headless run nobody can answer: list the open decisions with your recommended answers in the report, mark them unanswered, and never present a recommendation as the user's decision.

Language

Advisory (agent judgment): Talk to the user in the language they are using, including questions and option labels; keep command names, flags, file paths, skill names and other technical names unchanged.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free