Planning
Use when a task needs scope clarification, acceptance criteria, implementation slicing, dependency mapping, or a verification plan before coding begins. This skill turns fuzzy requests into concrete execution plans.
Install
$ agentstack add skill-motao123-dev-workflow-kit-planning ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-motao123-dev-workflow-kit-planning) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Planning
Use this skill before implementation when the task is unclear, large, risky, or cross-cutting.
Trigger Conditions
Use this skill when:
- the user asks how to approach a task
- requirements are incomplete or ambiguous
- the task spans multiple files, packages, or layers
- the team needs acceptance criteria before coding
- implementation order, risk, or dependencies are unclear
Do not use this skill for obvious one-line fixes or pure explanation-only questions.
Workflow
- Read the relevant code, docs, and local instructions first.
- Clarify the desired outcome and constraints.
- Break the work into the smallest meaningful slices.
- Identify risks, dependencies, and unclear assumptions.
- Define a concrete verification approach.
- Recommend the execution order.
Output
For non-trivial work, provide:
- goal summary
- scope boundaries
- step-by-step plan
- risks and dependencies
- verification plan
- recommended next skill if relevant
Coordination
After planning:
- continue in the active implementation workflow
- use
systematic-debuggingif execution stalls on unclear failures - use
ship-readinessbefore merge or release
Invocation Examples
- "Use planning to break this feature into implementation slices and acceptance criteria."
- "Use planning before we touch this multi-package refactor."
- "Use planning to define the safest order for this migration and its verification."
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: motao123
- Source: motao123/dev-workflow-kit
- License: MIT
- Homepage: https://motao123.github.io/dev-workflow-kit/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.