control-repo-manager
Use before answering project status or ending any session in this repo. Reads tracker truth from ops registries and event logs, distinguishes live upload verification from recorded sync evidence, and
SKILL.mdprojects/real-life-workflows/quarantine/imports/2026-07-07-market-research-agent/skills/control-repo-manager/SKILL.md
GitHubControl Repo Manager
Use this skill before answering project status in this repo. Use it before ending any session in this repo.
Skills-First Chat Contract
Contract phrase: Skills are the operator interface. Codex chat is the operator surface. The user never runs tracker scripts; scripts are internal adapters.
Skills are the operator interface. Codex chat is the operator surface. The user never runs tracker scripts; scripts are internal adapters that Codex may invoke after this skill decides tracker state is required.
Do not tell the user to run tracker commands, open a terminal, or execute Python. Codex performs tracker checks internally and reports the project status, sync status, blockers, and next workflow action in chat.
Source Of Truth
Project, repo, workstream, session, workflow-run, handoff, and sync status comes from:
ops/registry/*.jsonops/sessions/*.jsonlops/workflow-runs/*.jsonl
Folder scans, lane tables, README sections, AGENTS.md sections, and project surface inventories are audit evidence only. They can help explain drift, stale surfaces, or cleanup candidates, but they do not make a project active.
Deleted or stale surfaces must not be reported as active projects. If an old folder or stale lane table disagrees with the tracker, say that it is stale audit evidence and use tracker status as the active project answer.
Internal Adapter Actions
The tracker owns a callable command suite. Codex may inspect it internally with
the tracker-command-list and tracker-command-describe adapters, but the
suite is not a user terminal surface. Each callable command must stay
skills-owned by this skill and must remain marked as internal-only tracker
machinery.
Before answering project status, Codex internally checks tracker status:
npm run tracker:status
Before starting implementation work, Codex internally checks the project situation for the target project and proposed owned paths:
node scripts/control-repo.mjs tracker-status
If the user says they will edit, change, fix, update, revise, work on, or touch a tracked project, lane, skill, or workflow, Codex must create or lock a tracked skill run before asking what the edit is. Loaded context alone is not enough.
If the situation check reports risky parallel work, pause and ask the user whether to continue, join the existing run, or wait.
Use these Workflow Run internal adapters for Matt Pocock workflow work:
node scripts/control-repo.mjs tracker-session-start ...
node scripts/control-repo.mjs tracker-workflow-start ...
node scripts/control-repo.mjs tracker-workflow-checkpoint ...
node scripts/control-repo.mjs tracker-workflow-close ...
When auditing stale project surfaces, Codex internally runs:
npm run validate
Before ending a session, Codex internally runs the tracker gates that match the work performed:
npm test
npm run validate
npm run tracker:upload-gate
Session Completion Rule
A session is not complete until all of these are true:
- Tracker records are current.
- Workflow runs are completed, handed off, blocked, or abandoned.
- Intended changes are committed.
- The commit has been uploaded to GitHub.
- Upload verification has succeeded.
Do not treat a local clean tree or a recorded sync event as enough by itself.
Upload Truth
npm run tracker:status may use live git state for upload truth.
Recorded ops/sync state is evidence, not self-certifying truth.
Use this distinction when reporting status:
- live upload gate/status result: current upload truth;
- recorded
ops/syncentries: historical evidence that still needs live verification; - local folders or stale docs: audit evidence only.
If npm run tracker:upload-gate reports local changes still need
upload, say the session is not uploaded yet and do not report upload completion.
Workflow Currency
This repo uses the installed Matt Pocock skills as the tracker workflow currency. Do not use Superpowers planning or execution skills as the default process for tracker work. Workflow runs should record the Matt Pocock flow ID, phase skill, owned paths, validation commands, checkpoints, and closeout state.
Tracker records are skill-first. Every workflow run must answer these two questions before it can be valid:
- Which repo skill are we using or building?
- Which Matt Pocock phase skill are we currently in?
The repo skill is recorded as skill_id and skill_path, such as
agent-workflow-project-maker and
skills/agent-workflow-project-maker/SKILL.md. The phase skill remains
current_skill, such as grilling, to-prd, to-issues, implement, or
code-review.
If a tracker run does not have skill_id and skill_path, treat it as invalid
tracker state. The answer is not "make a command"; the answer is "name the
skill being built, then persist the run."
Workflow intake is an entry phase, not a waiting state after context is loaded.
Once a context manifest exists and the first context-aware question is ready,
checkpoint the run to current_skill=grilling before asking the user. If an
active run remains in workflow_intake with a context manifest attached,
tracker validation must fail and Codex must migrate the run to grilling
before continuing.