Skip to content
cccskills
FreePublished on GitHub

4x4

Work through sixteen open questions in four rounds to clarify major product decisions, risky changes, or large refactors. The agent adapts later questions to earlier answers, then turns your decisions into a step-by-step implementation plan.

OriginalShow the original description

Pull 16 fast decisions out of the user with 4 sets of 4 open questions, then present an implementation plan. Only for risky changes, large product decisions, or large refactors. Run when the user types /4x4. Agents may suggest it in one line but never start it on their own.

davidondrej/skills
See how to install

Good for

  • Clarifying decisions before a major product change
  • Planning a large refactor
  • Deciding rollout order for a risky change
  • Choosing how to handle likely edge cases

Files included (1)

  • SKILL.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

4x4

Get the user's judgment, taste, and decisions in 4 quick rounds. 16 open questions. A full run should take them 2–3 minutes.

The 4 sets

These are defaults. Adapt their names and focus to pull the most judgment and taste out of the user for this topic.

  1. Product — what it does, who it's for, UI/UX, scope.
  2. Software design — architecture, data, boundaries, what to reuse or delete.
  3. Practical — execution order, rollout, what ships first.
  4. Edge cases — the 4 most likely ways this breaks or surprises users. Each question asks how to handle one.

Workflow

  1. Load context fast. Use what's already in the thread. Skim only the files and docs that matter (scopes, ADRs, the diff). No research, no subagents.
  2. Pick the order. Start with the set whose answers most change the others.
  3. Pick 4 questions per set. Choose the 4 decisions with the biggest impact that only the user can make. Never ask what the code, docs, or common sense already answer. Skip anything already decided.
  4. Show one set at a time. Never preview or list the other sets. Stop and wait. Show the next set only after the user answers.
  5. Adapt. Rewrite later sets based on earlier answers.
  6. Present the plan. After set 4, give plain step-by-step instructions to execute the work properly, built from the user's answers. Chat only. Then stop. Don't build or write docs until the user says go.

Message format

## Set 2/4 · Software design

1. Where should X live?

2. ...

3. ...

4. ...

Nothing else. No intro, no outro.

Rules

  • Open questions only. Never give options, picks, recommendations, or hints. The point is the user's own thinking.
  • One short sentence per question. Concrete, plain English, clear on first read.
  • No meta questions, like how to measure success or what to test first. Ask about the work itself.
  • Vague or skipped answer: move on and use your judgment.
  • If the user calls a question bad, replace it or drop it. Your call.
  • If an answer contradicts an ADR or scope, point it out in the plan.
  • If an answer opens a big new question, note it in the plan. Don't add a 5th question.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

adr-verbatim

FreeSummary

Document approved decisions as concise ADRs, or architecture decision records. It preserves the user's meaning and conditions, removes conversational filler, follows the project's numbering, and presents the saved record for review.

  • Record a decision approved in conversation
  • Preserve the conditions and scope of a decision
  • Add a numbered ADR to existing records
davidondrej/skills4.2KUpdated Oct 21, 2026

anti-sleep

FreeSummary

Keep a Mac awake for a chosen duration or while a specified process runs. The skill uses built-in macOS tools to manage one session, verify that sleep prevention is active, and control whether the display stays on.

  • Keep a Mac awake during a lengthy task
  • Prevent sleep while a specified process runs
  • Allow the display to dim while keeping the Mac awake
davidondrej/skills4.2KUpdated Oct 21, 2026

ask-then-build

FreeSummary

Turn a feature or refactoring idea into a concise implementation prompt for another agent. It asks focused questions one at a time, records decisions, and includes development steps, validation, and working rules.

  • Clarify requirements for a new feature
  • Decide edge cases and failure behavior
  • Define the scope of a refactor
davidondrej/skills4.2KUpdated Oct 21, 2026

bb-cli

FreeSummary

Inspect and manage BB threads, environments, projects, and plugins through its command line interface. The skill guides agents to identify the correct targets, apply changes, and verify the resulting state.

  • Check BB projects and environment status
  • Manage skills and plugins
  • Create or operate threads
davidondrej/skills4.2KUpdated Oct 21, 2026

bb-plugins

FreeSummary

Create, install, and debug TypeScript plugins that extend bb with custom pages, sidebar panels, CLI commands, agent tools, themes, and other features. The skill also guides development reloads, log checks, and verification of installed plugins.

  • Add a custom page or sidebar panel to bb
  • Create a bb CLI command or agent tool
  • Investigate plugin errors through logs
davidondrej/skills4.2KUpdated Oct 21, 2026

before-building

FreeSummary

Identify one to three important decisions before starting a build. Based on the user's idea, this skill presents concise options and an initial recommendation for each, then waits for answers before work proceeds.

  • Clarifying important decisions before implementation
  • Deciding whether a solution needs to be reusable
  • Choosing between a short script and a separate module
davidondrej/skills4.2KUpdated Oct 21, 2026

See all skills by davidondrej

Report a problem with this skill