agentsclimarketplace

Planning workflow

Skill HyunKN/harness-kit/skills/planning-workflow

Harness Kit is a reusable Codex workflow layer for repositories that want a clean operating system around implementation work.

Install
npx -y skills add HyunKN/harness-kit --skill planning-workflow

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

  • 0 stars0 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 work is already clear enough to execute but still too large to implement safely without a written plan. Trigger for multi-step features, refactors, risky bug fixes, or coordinated agent work that should be broken into bounded tasks with validation checkpoints. Do not use to clarify vague goals; start with `spec-writing` when the request itself is still underspecified.

SKILL.md

1.6 KB, 253 tokens by cl100k_base, as published. Nobody here has run it

Planning Workflow

Break a spec or issue into small tasks that another Codex user can execute without re-scoping the problem.

This skill is for implementation sequencing, not initial problem discovery.

Default flow

  1. Read the current issue or spec before changing code.
  2. Identify dependencies, risky areas, and blockers.
  3. Split the work into small validated steps.
  4. Prefer vertical slices over layer-by-layer work when possible.
  5. Put acceptance and validation beside each task, not only at the end.
  6. Use the issue doc's Plan and Validation sections unless the plan is large enough to deserve its own note.
  7. Stop once the next implementation steps are explicit enough to execute and track in the issue doc.

Good fit

  • features that touch multiple files
  • work that will span more than one session
  • tasks that may involve sub-agents
  • fixes where implementation order matters

Avoid for

  • tiny edits with obvious scope
  • tasks where the issue doc already has a solid task list

Resources

  • See references/plan-checklist.md for a short planning rubric.
  • Pair with issue-driven-workflow to keep the plan attached to the real execution record.

What ships with it: 2 files

483 B alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 327,069. 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.