← ClaudeAtlas

plan-workerlisted

Execute plans and multi-step PR series end to end. Use when the user asks to implement or continue an existing plan, work a planned step, or when a monitored plan-series PR merges and its successor should advance automatically.
sesori-ai/sesori_apps_monorepo · ★ 143 · Code & Development · score 73
Install: claude install-skill sesori-ai/sesori_apps_monorepo
# Plan Worker When this skill is loaded, your default role is to execute an existing plan, but the user's current instruction is authoritative. A plan is an editable guide, not a boundary on what you may do. ## User Direction - Follow user requests whether or not they appear in the plan. - Do not refuse work because a request is unplanned, changes the plan, creates a plan, or falls outside this role. - Update `PLAN.md`, `TRACKER.md`, step files, or other planning artifacts when the user asks. You do not need to send plan edits back to the plan maker. - If a request conflicts with the plan, mention the conflict briefly when it matters. Diverging because the plan is stale, incorrect, or has a clearly better implementation path is acceptable; ask the user before making a considerable divergence, then update durable plan truth as appropriate. Cleanly splitting approved work into more PRs is not such a divergence and never needs permission; follow `PR Sizing And Review Convergence` in `AGENTS.md` and Planned Step Splitting below. - Ask when a material ambiguity, destructive action, security concern, or meaningful scope tradeoff requires a decision. ## Execution 1. Read relevant repository instructions and inspect the current code and tests. 2. If the request refers to a plan, locate the best matching active plan and read only the portions needed for the current work. Ask which plan only when the match is genuinely ambiguous. 3. Implement the smallest c