Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

factory-root-planner

Estrelas4

Forks1

Atualizado26 de abril de 2026 às 06:41

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.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

EduardoRemedios

EduardoRemedios/factory-starter-kit

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Gerentes de comprasOcupações de Gestão·SOC 11-3061

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	factory-root-planner
description	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.

Factory Root Planner

Workflow

Read AGENTS.md, docs/Factory/ORCHESTRATION.md, docs/Factory/Spec/STAGE_CONTRACTS.md, and docs/Factory/SCRATCHPAD.md ## Active Pitfalls (Mandatory).
Run bash scripts/knowledge_lint.sh before Stage A and persist output as docs/Factory/runs/<RUN_ID>/KNOWLEDGE_LINT.txt.
Create the run root and required files: raw_brief.md, EXECUTION_MODE.txt, CONTEXT_RECALL_REPORT.md, and later SPRINT_ID.txt.
Build recall evidence with ./scripts/factoryctl context-index and ./scripts/factoryctl context-report --profile stage-a.
Keep the run PLANNING_ONLY unless the raw brief explicitly authorizes EXECUTION_ENABLED.
Coordinate stages in order: A -> B -> C -> D -> E -> F -> G -> H -> I -> J -> I2.
After each stage handoff, run ./scripts/factoryctl stage-lint --run <RUN_ID> --stage <STAGE>.
After I2, run ./scripts/factoryctl pack-lint --run <RUN_ID> before human review.

Guardrails

Do not execute sprint implementation during Factory planning.
Do not expand scope silently; record proposed expansion as BLOCKING unless approved.
Treat recall artifacts as evidence aids, not authority.
If Coverage Verdict: WEAK, halt and repair recall before drafting intent.
If any validator fails, fix the artifact or re-run the affected stage before advancing.

Outputs

Return:

run id
execution mode
evidence paths created
current stage status
validator results
blockers requiring human decision

Mais deste repositório

mesmo repositório

factory-execution-closeout

EduardoRemedios/factory-starter-kit

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.

2026-04-264

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-264

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-264

name	factory-root-planner
description	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.

Factory Root Planner

Workflow

Read AGENTS.md, docs/Factory/ORCHESTRATION.md, docs/Factory/Spec/STAGE_CONTRACTS.md, and docs/Factory/SCRATCHPAD.md ## Active Pitfalls (Mandatory).
Run bash scripts/knowledge_lint.sh before Stage A and persist output as docs/Factory/runs/<RUN_ID>/KNOWLEDGE_LINT.txt.
Create the run root and required files: raw_brief.md, EXECUTION_MODE.txt, CONTEXT_RECALL_REPORT.md, and later SPRINT_ID.txt.
Build recall evidence with ./scripts/factoryctl context-index and ./scripts/factoryctl context-report --profile stage-a.
Keep the run PLANNING_ONLY unless the raw brief explicitly authorizes EXECUTION_ENABLED.
Coordinate stages in order: A -> B -> C -> D -> E -> F -> G -> H -> I -> J -> I2.
After each stage handoff, run ./scripts/factoryctl stage-lint --run <RUN_ID> --stage <STAGE>.
After I2, run ./scripts/factoryctl pack-lint --run <RUN_ID> before human review.

Guardrails

Do not execute sprint implementation during Factory planning.
Do not expand scope silently; record proposed expansion as BLOCKING unless approved.
Treat recall artifacts as evidence aids, not authority.
If Coverage Verdict: WEAK, halt and repair recall before drafting intent.
If any validator fails, fix the artifact or re-run the affected stage before advancing.

Outputs

Return:

run id
execution mode
evidence paths created
current stage status
validator results
blockers requiring human decision