methodical

Plugin methodical from marketplace methodical in BigLeverVentures/methodical-gated-engineering. Commands read from the repo's manifest — 20 days ago.

Skills (9)

• brainstorm

  Explore what to build and why, and record it in docs/brainstorms/, before any plan exists. Use when the user starts a new unit of work (a feature, a fix with unclear scope, a redesign) and docs/plans/ has no plan for it. First step of the methodical loop. Not for questions or reviews that change no

• compact

  Write the resume point in docs/resume.md, every ruling verbatim, so the context can be compacted without losing anything. Use when the context window is half full or more, or when the user asks to compact or for a resume point; not after every merge. Last step of the methodical loop. Not for the com

• compound

  Write up each non-obvious problem a unit solved in docs/solutions/, index it, and update the resume point. Use after every unit's work review clears (it writes up what was non-obvious, if anything, then asks before merging unless the repo records a standing merge grant), and always when the user say

• 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.

• north-star

  Make sure the project has a written goal in docs/north-star.md, then state how the current unit moves toward it. Use after a brainstorm and before a plan, or when substantial work is requested in a repo with no docs/north-star.md. North-star step of the methodical loop. Not to rewrite an existing on

• 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 reviewin

• 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 loo

• 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 fo

• 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

Slash commands (1)

• /methodical:rules

  Show the Methodical Adaptive Gated Engineering rules and the current model routing table.

Hooks (7)

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/hooks/hook.cjs"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/hook.cjs"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/hook.cjs"

• PostToolUseFailure

  node "${CLAUDE_PLUGIN_ROOT}/hooks/hook.cjs"

• SubagentStop

  node "${CLAUDE_PLUGIN_ROOT}/hooks/hook.cjs"

• PreCompact

  node "${CLAUDE_PLUGIN_ROOT}/hooks/hook.cjs"

• PostCompact

  node "${CLAUDE_PLUGIN_ROOT}/hooks/hook.cjs"

Similar plugins