AGENT SKILL

deepen

Test a plan's risky assumptions by executing them, and fold the findings into the plan before review. Use when a plan in docs/plans/ meets the deepen triggers, its base commit is stale, or the user asks to deepen it. Deepen step of the methodical loop. Not for writing a plan or reviewing code.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 0
Forks
0

01 前言 Front Matter

name
deepen
description
Test a plan's risky assumptions by executing them, and fold the findings into the plan before review. Use when a plan in docs/plans/ meets the deepen triggers, its base commit is stale, or the user asks to deepen it. Deepen step of the methodical loop. Not for writing a plan or reviewing code.

03 SKILL.md 正文

Deepen

Say Step: deepen before anything else, with the score that triggered it.

If the user skips it, go to plan-review.

What it produces

One findings file per question, in docs/plans/<plan-file-name-without-.md>/deepen/<question>.md, and a revised plan that folds them in. Each finding says whether it was executed (a command was run, its output quoted) or only read (from docs or code). Why: a claim read from documentation is a hypothesis; the point of deepening is to turn the ones the plan depends on into facts.

How

  1. List the questions. Each trigger that scored becomes one or more questions the plan's correctness depends on: "does the parser see X?", "does the library behave like Y when Z?", "has this been solved in docs/solutions/?".
  2. Seat them. Research seats run on the worker's row, or on the decider's row when the plan's escalation: is lean or full (Escalation in ${PLUGIN_ROOT}/reference/seat-selection.md); the code-grounded and rigor seats that check the plan's claims against the code run on the decider's row. Each seat names its row's model and effort. Give each seat the plan's base commit, the sections it rules on, and what not to read whole; never forbid a seat from opening a file it needs. Why: a scoped brief spends judgment on the question, not on rereading the repo.
  3. Execute where you can, in a scratch directory, never against the user's real configuration or data. If a check would cost money or cannot be undone, stop and ask with the native structured-question tool.
  4. Fold the findings into the plan as a new revision: update the inventory, approach and tests; record what changed and why at the top. Update base: if the code moved; the plan stays state: draft.

When it hands on

Say Step: plan-review and run /methodical:plan-review on the revised plan in the same turn.

04 同仓库更多 Skills

BigLeverVentures
BigLeverVentures/methodical-gated-engineering

phrase-outside

暂无简介

★ 0
BigLeverVentures
BigLeverVentures/methodical-gated-engineering

named-only

暂无简介

★ 0
BigLeverVentures
BigLeverVentures/methodical-gated-engineering

work

Build an approved plan from docs/plans/ on its own short-lived branch, or a change the user said to make without a plan. Use when a plan reads state: approved and the user wants it built, when resuming such a build, or when the user has waived the plan for a named change. Work step of the methodical loop. Not when no approved plan exists and the user has not waived one (run the plan step), and not for reviewing finished work.

★ 0
BigLeverVentures
BigLeverVentures/methodical-gated-engineering

work-review

Review a finished build on its branch against its plan, with reviewer seats matched to the code's language, before it merges. Use when the work step's tests pass and the plan's approach is done, or when the user asks for a review of a branch's changes. Work-review step of the methodical loop. Not for reviewing a plan.

★ 0
BigLeverVentures
BigLeverVentures/methodical-gated-engineering

plan

Write the plan file in docs/plans/ that code changes get before building, unless the user has said to build without one. Use when the user asks to build, fix, edit or change code and docs/plans/ has no approved plan for it, or when a plan must be revised after review. Plan step of the methodical loop. Not for questions or reading code, and not when the user has waived the plan for this change (go to work).

★ 0
BigLeverVentures
BigLeverVentures/methodical-gated-engineering

plan-review

Review a plan in docs/plans/ with reviewer seats matched to the project's language, before the user approves it. Use when a plan has just been written or deepened, when a plan was revised after review, or when the user asks for a plan review. Plan-review step of the methodical loop. Not for reviewing built code.

★ 0