Guides feature and bug-fix planning from concept through specs to tracker tickets.
npx skills add https://github.com/xriu/dotfiles --skill work-plan-xriu
Please help me install this Agent Skill. Skill: work-plan Source: https://github.com/xriu/dotfiles/tree/main/home/.skills/work-plan Command: npx skills add https://github.com/xriu/dotfiles --skill work-plan-xriu
ready-for-agent label and breaks it into tracer-bullet tickets with declared blocking edges. - Context hygiene management: Prescribes handoff strategies to keep the full planning session within one context window without losing information. - Use Case: You need to add a payment retry feature. Anchor the change in one paragraph, grill open questions into a CONTEXT.md and ADRs, formalize requirements, generate a spec, optionally build a typed skeleton, then publish small implementable tickets to your tracker. ## Quick Start Ask the AI to start a work plan for your feature or bug fix and describe the change you want to make in one paragraph.High-intent search queries and answers about installing and using this skill.
Start by anchoring the change in one paragraph describing the feature, its audience, and the problem it solves. Then grill open questions into a CONTEXT.md and ADRs, formalize requirements, write a spec, and break it into small tickets each implementable in one session.
Use the to-tickets step, which breaks the spec into tracer-bullet tickets. Each ticket declares its blocking edges, has clear acceptance criteria, and is sized to be implemented in a single session.
Skip prototyping when every design question settles in conversation without needing runnable code. Skip the docs-to-types step when the change is small or a single TDD slice, since typed skeletons are not meant for the first slice.
Yes, the workflow supports resuming by stating which step you are on, such as saying you are at step 3. Completed steps are skipped and the workflow continues from that point with its gate criteria.
The workflow requires companion skills for each step and a configured issue tracker with triage labels before publishing specs or tickets. It also depends on keeping one unbroken context window, using handoff rather than compaction near token limits.
jwh3timesBreak plans and specs into tracer-bullet tickets with declared blocking edges.
richard-jh-mccraeBreaks plans or specs into tracer-bullet tickets with declared blocking edges published to a tracker.
mmnavarrPlans large multi-session efforts as issue-tracker maps of investigation tickets.
micfreImplement planned BMILD Slices, fix bugs, and build prototypes.