agentsclimarketplace

Plan update

Skill yarlson/yarstack/plugins/yarstack/skills/plan-update

Engineering workflows and standards for Codex and Claude Code: plan, implement, test, review, and deliver repository changes.

Install
npx -y skills add yarlson/yarstack --skill plan-update

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Make the smallest evidence-backed correction to implementation-plan mechanics. Use when implementation or validation proves incorrect ordering, prerequisites, phase scope, dependencies, steps, or validation gates.

SKILL.md

1.6 KB, as published. Nobody here has run it

Plan Update

Correct an implementation plan without making product, architecture, or behavior decisions.

Workflow

  1. Identify the authoritative plan, exact mechanical defect, evidence, and affected phases.
  2. Confirm that the correction is local. Use plan-create when multiple phases require broad replanning.
  3. Use spec-update when the defect concerns product behavior, architecture semantics, a public contract, or acceptance meaning. Use architecture-refine when runtime architecture remains unsettled.
  4. For plans affecting long-running or distributed workloads, verify established guarantees cover restarts, rolling replacement, concurrent replicas, in-flight or duplicate work, partial failure, and recovery. Repair omissions only when repository evidence or a settled contract determines the behavior.
  5. Stop for user direction when the correction materially expands authorized scope.
  6. Apply the smallest correction in the plan's existing structure and style.
  7. Verify affected dependencies, cross-references, invariants, environmental and failure assumptions, acceptance evidence, and downstream phases remain consistent.

Do not use plans as progress logs, add speculative roadmap work, rewrite unrelated phases, or disguise scope expansion as maintenance.

Finish by reporting the defect, evidence, exact correction, affected phases, and whether implementation or validation can safely resume.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.