Auditing project readiness
Skill VKK-00/agentic-project-lifecycle/plugins/agentic-project-lifecycle/skills/auditing-project-readiness
Codex plugin for governing large software projects from discovery through release and operations.
npx -y skills add VKK-00/agentic-project-lifecycle --skill auditing-project-readinessAssembled 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 checking whether a project, feature, migration, or release is ready to advance; when requirements, tests, evidence, owners, context boundaries, rollout, rollback, or project health may be incomplete or inconsistent.
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
2.0 KB, as published. Nobody here has run it
Auditing Project Readiness
Prefer deterministic checks for mechanically verifiable claims. Use judgment only after schemas, links, commands, and required evidence pass.
- RULE-AUDIT-01: Run relevant bundled validators before stating readiness. Report every blocking condition with the artifact, owner, and expected correction.
- RULE-AUDIT-02: Require traceability from requirement to implementation feature, verification test, evidence, and release. Do not treat document presence as proof of behavior.
- RULE-AUDIT-03: Build a task-specific context packet containing only the goal, approved decisions, relevant contracts, allowed/forbidden paths, and verification commands. Reject path traversal and unrelated repository dumps.
- RULE-AUDIT-04: Collect fresh command exit codes, durations, and logs. Never replace observed evidence with an agent's statement that checks passed.
- RULE-AUDIT-05: Block release readiness when owner, support, telemetry, rollout, rollback, migration, restore, or critical-risk evidence required by the release stage is missing.
- RULE-AUDIT-06: Do not promote a process skill to stable based only on static checks or synthetic fixtures. Require executed baseline-versus-skill behavior evaluation, acceptable held-out false-positive triggering, multiple non-fixture project trials, execution-trace review, leave-one-rule-out ablation, and explicit evaluator limitations.
Use scripts under scripts/ for state validation, traceability, context packing, verification collection, release readiness, and health reporting. Read audit contract before interpreting a pass.