Loading...
Loading...
Found 10 Skills
Internal/shared core rules for design-tree skills. Use only when maintaining the design-tree system itself or when another design skill needs shared governance rules for derivation, handoff, boundaries, or anti-bloat controls. Do not trigger for ordinary user design requests, and do not use as a replacement for design-orchestrator, design-structure, or design-refinement.
A relentless interview that asks every frontier question at once, round by round.
Interview the user relentlessly about a plan, idea, or project until a shared understanding is reached. Walks down each branch of the design tree, resolving dependencies between decisions one-by-one. Use when starting something new or when a plan needs rigorous thinking-through.
Continuous follow-up interviews, presenting all questions on the current frontier in each round.
Refine an existing design tree until key branches become implementation-ready. Use when the high-level structure already exists but important branches remain vague, shallow, or unresolved. Trigger when the user needs deeper decomposition, edge-case coverage, failure-path clarification, interface detail, or validation criteria for a partially designed system. Do not use to create the initial design skeleton from scratch or to compare options for a single explicit decision node.
Build the initial design structure from a vague or partially formed idea. Use when the task lacks a clear design tree, scope boundaries, core objects, key flows, or explicit decision points. Trigger when the user has an idea, feature request, or system goal that needs to be turned into a structured design skeleton before deeper refinement. Do not use when the design tree already exists and the main need is to deepen or validate it.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Grill the user's plans, decisions, or ideas layer by layer. Use this when the user wants to stress-test their thinking or uses any 'grill' trigger phrase.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking or uses any "grill" trigger phrases. Enable documentation mode only when the user explicitly asks to capture decisions, ADRs, or glossary entries during the session.
Grills the user relentlessly about a plan, decision, or idea until both sides reach a shared understanding. Maps the subject as a design tree and interviews in rounds — each round asks every question whose prerequisites are already settled, with answer options and a recommended answer, then waits. Use when the user wants to stress-test their thinking, pressure-test a plan or a design, or uses a "grill" trigger phrase.