Generate a task-by-task implementation plan from an approved design doc.
npx skills add https://github.com/bketelsen/ytsejam --skill write-plan-bketelsen
Please help me install this Agent Skill. Skill: write-plan Source: https://github.com/bketelsen/ytsejam/tree/main/contrib/skills/write-plan Command: npx skills add https://github.com/bketelsen/ytsejam --skill write-plan-bketelsen
Designs and product specs often stall in a shared doc, delaying delivery and muddying responsibility. This skill translates an approved design into a concrete implementation plan and a repeatable workflow. It also sets up a temporary worktree to keep changes isolated and ready for review.
Confirm the design is approved and run the write-plan flow to generate a concrete implementation plan in docs/plans
High-intent search queries and answers about installing and using this skill.
To turn an approved design document into an executable development plan, generate a structured markdown plan with explicit tasks and milestones, while setting up a dedicated git worktree to isolate changes. This creates a ready handoff for execution.
To isolate new feature changes using a git worktree, create a temporary worktree branching off the main repository state. This keeps uncommitted modifications separate and ready for baseline validation before merging.
The best way to structure a task-by-task implementation plan is to write a markdown document detailing specific files, tasks, and milestones. This structured plan provides a clear workflow feeding directly into the development phase.
Yes, you need a validated repository state and a main branch to generate an implementation plan. The process requires a stable baseline to run gate tests and create an isolated git worktree for commit-ready changes.
You should store design specs and implementation plans inside the docs/plans/ directory. The workflow expects an approved design at docs/plans/YYYY-MM-DD-topic-design.md and outputs the corresponding plan as docs/plans/YYYY-MM-DD-feature-name.md.
Approved designs stall in shared docs because responsibility and execution steps remain unclear. You automate the handoff by translating the design into a concrete task-by-task plan with commit-ready changes and baseline validation.
niznik-devDuplicate the previous weekly agenda into a new YYYY-MM-DD-SM.md file and update the wiki index.
bestdanExecute complex task graphs autonomously in an isolated worktree.
steven-3Create isolated Git worktrees with baseline test verification.
CC90210Create and manage isolated git worktrees for parallel branch development.
