SKILLEMALL.ai
GitHub ↗ RU Sign in

BF implementation-planning

Plan the implementation of an approved requirement or specification: produce an executable, dependency-aware delivery plan covering work breakdown, dependency mapping, critical path, ownership, parallelism and sequencing, rollout strategy, rollback and recovery paths, and verification against the original requirement. Supports cross-team, cross-repository, migration, and staged-rollout scenarios. Do not use for pre-approval discovery or needs-finding, authoring a specification from scratch, coding or implementation, the neckbeard issue-to-PR delivery flow itself, or any work whose prerequisite decision has not been approved — planning unapproved work is an explicit stop condition.

magnus919/agent-skills Agent Skills author: magnus919 MIT 7 files body ≈ 2 784 tokens Open the sourcegithub.com↗ analyzed 27 h ago

Plan the implementation of an approved requirement or specification: produce an executable, dependency-aware delivery plan covering work breakdown, dependency…

As a process F 49/100 · Will not run — References files that are not bundled: ../product-discovery/SKILL.md, ../spec-driven-development/SKILL.md, ../backend-engineering/SKILL.md

AnalyzerSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
77
Run on models
none yet
Process rating
F
49/100
Will not run
References files that are not bundled: ../product-discovery/SKILL.md, ../spec-driven-development/SKILL.md, ../backend-engineering/SKILL.md
Tools and files w 18
0
Result and completion w 14
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../product-discovery/SKILL.md
  • warning missing-ref reference to a missing file: ../spec-driven-development/SKILL.md
  • warning missing-ref reference to a missing file: ../backend-engineering/SKILL.md
  • warning missing-ref reference to a missing file: ../frontend-engineering/SKILL.md
  • warning missing-ref reference to a missing file: ../software-architecture-analysis/SKILL.md
  • warning missing-ref reference to a missing file: ../bmad/SKILL.md
  • warning missing-ref reference to a missing file: ../technical-project-management/SKILL.md
  • warning missing-ref reference to a missing file: ../technical-program-management/SKILL.md
  • warning missing-ref reference to a missing file: ../adr-authoring/SKILL.md
  • warning missing-ref reference to a missing file: ../release-engineering/SKILL.md
  • warning missing-ref reference to a missing file: ../site-reliability-engineering/SKILL.md
  • warning missing-ref reference to a missing file: ../qa-methodology/SKILL.md
  • warning missing-ref reference to a missing file: ../platform-engineering/SKILL.md
  • warning missing-ref reference to a missing file: ../secure-software-engineering/SKILL.md
  • warning missing-ref reference to a missing file: ../api-design-and-evolution/SKILL.md
  • warning missing-ref reference to a missing file: ../data-engineering/SKILL.md

Process rating: all ten parameters 49/100

Will not run. References files that are not bundled: ../product-discovery/SKILL.md, ../spec-driven-development/SKILL.md, ../backend-engineering/SKILL.md
  • 0Tools and files. 16 referenced file(s) missing: ../product-discovery/SKILL.md, ../spec-driven-development/SKILL.md, ../backend-engineering/SKILL.md
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 1 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 33 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2784 tokens
  • low No test case covers injection arriving through data

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
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 689: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 33 items
  • +4Reference files are cited in the instructions (1 of 1)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.