Factory execution closeout
Skill EduardoRemedios/factory-starter-kit/.agents/skills/factory-execution-closeout
Close implementation work against an approved Factory pack. Use when Codex is asked to verify execution after human Go, compare a code/doc diff to the approved envelope and micro-sprints, prepare execution completion notes, check residual risk, or decide whether a completed implementation is ready for project-specific merge gates.From its SKILL.md
npx -y skills add EduardoRemedios/factory-starter-kit --skill factory-execution-closeoutAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 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.
SKILL.md
1.5 KB, as published. Nobody here has run it
Factory Execution Closeout
Workflow
- Confirm execution was explicitly authorized and the run is
EXECUTION_ENABLED. - Read the approved envelope, micro-sprints, verification plan, traceability matrix, and pack audit report.
- Compare actual changes against scope, non-goals, file-touch budgets, and stop/go gates.
- Run the project-specific verification commands from
AGENTS.mdand the pack. - Record evidence paths for tests, lint, screenshots, reports, or manual checks.
- Identify residual risk and any deviation from the approved pack.
- Do not merge or request merge if required project gates fail.
Closeout Decision
READY: implementation matches the approved pack and required verification passed.BLOCKED: verification failed, scope drift occurred, or required evidence is missing.NEEDS HUMAN DECISION: implementation is technically complete but a product, policy, or scope decision is unresolved.
Outputs
Return:
- execution status
- files changed
- verification commands and results
- pack alignment notes
- residual risks
- merge-readiness blockers