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](../../references/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...