Run any Skill in Manus with one click

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.

Run Skill in Manus

Overview

Install command

npx skills add https://github.com/EduardoRemedios/factory-starter-kit --skill factory-execution-closeout

Copy and paste this command into Claude Code to install the skill

Source

EduardoRemedios/factory-starter-kit

Stars3

Forks1

UpdatedApril 26, 2026 at 06:41

File Explorer

2 files

SKILL.md

readonly

name	factory-execution-closeout
description	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.

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.md and 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

More from this repository

same repository

factory-pack-consolidator

EduardoRemedios/factory-starter-kit

Consolidate a Factory pack during Stage J. Use when Codex is asked to create or repair PACK_MANIFEST.md, create or repair PACK_CHECKLIST.md, verify required pack artifacts are present and non-empty before Stage I2, instantiate the Purple Gate checklist, or prepare a completed pack for pack-lint.

2026-04-263

factory-purple-gate

EduardoRemedios/factory-starter-kit

Perform Factory Purple Gate adjudication against evidence. Use when Codex is asked to review Stage D or Stage I2, decide PASS, CONDITIONAL PASS, or FAIL, evaluate PACK_CHECKLIST.md, resolve Red/Blue disputes, assess whether scope expansion remains unapproved, or produce PACK_AUDIT_REPORT.md from completed Factory artifacts.

2026-04-263

factory-root-planner

EduardoRemedios/factory-starter-kit

Coordinate a Factory run from raw brief through Stage I2. Use when Codex is asked to initialize a Factory run, run Stage A, create or repair run-root evidence, enforce Factory read order, choose PLANNING_ONLY versus EXECUTION_ENABLED posture, coordinate the full stage flow, or prepare a pack for human review without executing implementation.

2026-04-263

Source

EduardoRemedios

EduardoRemedios/factory-starter-kit

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

name	factory-execution-closeout
description	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.

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.md and 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