AD task-planning
Generates phased, dependency-ordered implementation tasks from specifications. Use after spec is complete and before starting implementation
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches
How to improve
For the model run — optional
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_plugin"
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (task-planning) differs from the folder (nm-spec-kit-task-planning)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 32 steps
- 100Execution cost. Instruction body is 760 tokens
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 140: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.
External checks
ClawHub: clean
This is a documentation-only task-planning skill whose behavior matches its stated purpose, with only a minor risk that broad triggers may activate it more often than intended.
LLM: benign (high) · VirusTotal: · 26 Aug 2026