Repository navigation
feat(plan-work-items): classify each item's implementation, review, and expected paths - #226
Merged
mxriverlynn merged 1 commit intoOct 15, 2026
Conversation
…nd expected paths Enrich the producer so each work item carries the markers the downstream driver needs, without pulling in the driver itself: - Add a Type field (deliverable / audit / spike) and rename Tests -> Checks in the work-item template. - Add Suggested implementation, Suggested review, Requires pre-work decisions, and Expected paths fields, selected via a new deliverable-skill catalog. - Direct project-manager to derive those markers and expected paths, and close the run with the three-bucket (unattended / pauses-for-human) recommendation. - Reframe the upstream unverified-assumptions guidance onto Requires pre-work decisions, since item-level HITL/AFK moves to the per-marker model. Split out of feat/autonomous-driver-core-loop as a standalone producer-side change; carries no implement-work-items edits. Rebased onto v6.0.0-beta, resolving conflicts with the reworked skill: - The breakdown is now dispatched to plan-synthesizer, not project-manager; the new directives sit beside the Justification and drafting-order ones. - v6 removed the separate Tests block, so there is no Checks block; the audit and spike check guidance moved into Acceptance criteria. - Summary stays first; the classification fields (Type, Requires pre-work decisions, Suggested implementation/review, Expected paths) render after Acceptance criteria and before Depends on. - Catalog skill namespaces updated for skills that moved out of han-core (han-documentation, han-research). - Long-form doc changes ported to han-planning/docs/skills/plan-work-items.md; links to the not-yet-merged implement-work-items doc dropped. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-Authored-By: River Bailey <river.bailey@testdouble.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BvgX88kC9h9xbe4zGLf7BC
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces #111 by @taminomara, rebased onto
v6.0.0-betato resolve its merge conflicts. The original branch lives on a fork we can't push to, so this PR carries the same commit with @taminomara kept as the commit author. All credit for the change is theirs.What the change does
plan-work-itemsnow records, for each work item, which skill or agent should build it and which should review it, and whether each part can run unattended (AFK) or needs a human (HITL). Each item also records aType(deliverable,audit, orspike), whether it needs a human decision before work starts, and the files it is expected to touch. A new deliverable-skill catalog maps each kind of deliverable to its suggested implementation and review.How the conflicts were resolved
The skill changed a lot on
v6.0.0-betasince #111 was opened, so the resolution adapts the change to the new shape rather than replaying it line for line:plan-synthesizer, notproject-manager. The new directives sit beside the existing justification and drafting-order directives.v6.0.0-betaremoved the separateTestsblock, so there is noChecksblock. The audit and spike check guidance moved intoAcceptance criteria.Summarystays first. The classification fields (Type,Requires pre-work decisions,Suggested implementation,Suggested review,Expected paths) render afterAcceptance criteriaand beforeDepends on.han-core(han-documentation:*,han-research:research).han-planning/docs/skills/plan-work-items.md. Links to theimplement-work-itemsdoc were dropped, since that skill isn't in this repo yet;SKILL.mdstill offers it only when it is available.Open from #111
The original PR was a draft, and @taminomara noted
auditandspikewere meant to merge into one type before it was ready. That is still open, so this PR is also a draft.