agentsclimarketplace

Planning

Skill motao123/dev-workflow-kit/planning

21 markdown-first software delivery workflow skills for Claude Code, Codex, and compatible agents. Standalone skill kit covering planning, debugging, CI, review, security, rollout, performance, data quality, and post-incident workflows.

Install
npx -y skills add motao123/dev-workflow-kit --skill planning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.7 KB, as published. Nobody here has run it

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

  1. Read the relevant code, docs, and local instructions first.
  2. Clarify the desired outcome and constraints.
  3. Break the work into the smallest meaningful slices.
  4. Identify risks, dependencies, and unclear assumptions.
  5. Define a concrete verification approach.
  6. 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-debugging if execution stalls on unclear failures
  • use ship-readiness before 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."

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.