BF write-plan
Use when you have a finalized brainstorm-beagle spec at `.beagle/concepts/<slug>/spec.md` and need a bite-sized, TDD-driven implementation plan before any code is written. Triggers on: "write a plan", "plan this spec", "turn the spec into a plan", "now plan the implementation", "write-plan". Reads the spec, designs the file structure, decomposes work into 2-5 minute TDD steps with exact paths and commands, self-reviews against the spec, gets user approval, then writes to `.beagle/concepts/<slug>/plan.md` and offers to generate an execution handoff prompt via the subagent-prompt skill. Does NOT brainstorm specs, write code, or execute the plan — produces the plan document (and an optional handoff prompt) only.
As a process F 54/100 · Will not run — References files that are not bundled: ../brainstorm-beagle/SKILL.md, ../../../beagle-core/skills/subagent-prompt/SKILL.md
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 10339 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../brainstorm-beagle/SKILL.md - warning
missing-refreference to a missing file: ../../../beagle-core/skills/subagent-prompt/SKILL.md
Process rating: all ten parameters 54/100
- 0Tools and files. 2 referenced file(s) missing: ../brainstorm-beagle/SKILL.md, ../../../beagle-core/skills/subagent-prompt/SKILL.md
- 0Result and completion. Does not say what the result is
- 30Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 10339 tokens: crowds the task out of the window
- 85Steps. 117 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 28 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 24 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (20 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 718: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 117 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.