Rescuing software projects
Skill VKK-00/agentic-project-lifecycle/plugins/agentic-project-lifecycle/skills/rescuing-software-projects
Codex plugin for governing large software projects from discovery through release and operations.
npx -y skills add VKK-00/agentic-project-lifecycle --skill rescuing-software-projectsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 16 days oldThe repository was created 16 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 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
Use when a software project is late, repeatedly missing commitments, blocked by failing builds or deployments, carrying uncontrolled scope, lacking clear ownership, or requiring a recovery plan before normal feature work can continue.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.6 KB, as published. Nobody here has run it
Rescuing Software Projects
Restore control before optimizing architecture or adding scope. The first outcome is reliable visibility and a small confidence-restoring release.
- RULE-RESCUE-01: Freeze new scope temporarily. Establish a reproducible build, test, deployment, and status view; record what is actually working rather than relying on plans or confidence.
- RULE-RESCUE-02: Inventory commitments, owners, dependencies, blockers, and the critical path. Mark commitments as keep, renegotiate, defer, or cancel with an accountable decision owner.
- RULE-RESCUE-03: Classify blockers as product, technical, dependency, people/ownership, operational, or decision latency. Remove non-critical work and create the smallest release that restores trust or usable value.
- RULE-RESCUE-04: Do not start a broad rewrite or platform migration unless it directly removes the current critical-path blocker and has a reversible proof point.
- RULE-RESCUE-05: Track daily evidence: passing checks, deployability, blocker age, decision latency, scope change, and remaining risk. Re-baseline roadmap and ownership only after the recovery release is stable.
Read triage, recovery planning, and rebaseline.