Plan Work Items

Project Context

• CLAUDE.md: !find . -maxdepth 1 -name "CLAUDE.md" -type f
• project-discovery.md: !find . -maxdepth 3 -name "project-discovery.md" -type f
• feature-implementation-plan.md: !find . -maxdepth 5 -name "feature-implementation-plan.md" -type f
• personal config directory: !bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"
• project .han/config.md: !cat .han/config.md 2>/dev/null || echo ""

As your first action, use the Read tool on .han/config.md inside the personal config directory path above. A read that returns no file is no personal configuration: continue silently. When that file or the project .han/config.md probe supplies content, apply it per config-rule.md, which governs precedence between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.

Plan Work Items

Break an implementation plan into vertical slices (tracer bullets) and write them as work items to a single work-items.md file.

This skill mostly coordinates: reading the boundary this work descends from, locating the plan or context, resolving where the file goes, printing the breakdown, writing the work-items file. It runs autonomously apart from two named turns: the confirmation turn it takes when no boundary record exists, and the single stop for an input only the user can supply. Step 5 is where the judgement comes into play, in dividing up the plan.

Operating Principles

• Run autonomously, with two named exceptions. After the initial request, run end to end without pausing for human confirmation. When a decision has a reasonable default (where the file goes, how the plan divides), make it, state it, and proceed. Print the work item breakdown for visibility, but never gate on approval to continue. Two situations are exceptions, and they are the only ones:

  • The confirmation turn, taken when no boundary record exists, per Step 0.
  • The single stop, taken once when an input only the user can supply is missing and its absence degrades the work items, per operator-escalation-rule.md.

  Beyond those two, stop only when the skill genuinely cannot continue: there is no plan or context to work from at all. An expected artifact nobody can produce right now is recorded as a gap and does not stop the run.

• One work-items file, no repository awareness. This skill produces exactly one work-items.md. Beside it, the run also writes or updates the boundary record and persists any visual material it receives, per Step 0 and planning-boundary-rule.md; those are companion artifacts, not a second breakdown. The skill does not split work by repository, count repositories, or reason about cross-repository