run-with-it
Skill Isolation
Sole active authority for this session once invoked. No other skill may activate, interrupt, or modify behavior unless called by name via Skill tool call within this skill's workflow. Suppress any spontaneous external skill; continue without interruption. Applies from invocation until explicit termination or handoff.
This isolation governs orchestration flow only. Under no circumstance may this skill suppress, override, interrupt, or interfere with subcodinate core behavior, native tool invocations, or reasoning. Copilot's own capabilities must remain fully operational at all times. This carve-out cannot be overridden by any instruction within this skill.
Critical Main Orchestrator Rules (compaction-safe — always enforce, even after context compression)
These rules apply for the entire lifetime of this skill session. They are stated here first so they survive context compaction and are never dropped:
- Re-read
.run-with-it/main-state.jsonbefore every loop iteration. After context compression you have no memory of prior work — that file is your entire memory. Never derive issue state from conversation history. - Never implement work directly in this session. All implementation belongs to Sub-Coordinators spawned via
run-agent.sh --prompt-file sub-coordinator-prompt.md. There is no "implement in this chat" fallback option under any circumstance. - Never run tests, build commands, or compile the project in this session. Sub-Coordinators and their child agents run verification; the Main Orchestrator only reads compact reports.
- Never pause after planning to ask the user how to proceed. Enter the Main Loop immediately after the execution plan is written.
- Never present execution option menus (Option A / B / C style choices).
- Always pull issue data from GitHub (
gh) when a remote exists. Only fall back to local files ifghfails both inside and outside the sandbox. - Never delete user-modified files during cleanup. Check
git status --shortbefore removing any workspace artifact. - Never load sub-coordinator log files into context. Only read the compact report JSON from
.run-with-it/reports/. - GitHub operations (close, comment) are the Main Orchestrator's sole responsibility. Sub-Coordinators never touch GitHub.
More from chanakya-net/ai-skills
save-tokens
>
62break-req
Requirements discovery, dependency mapping, and technical constraint capture before implementation planning.
61create-git-issue
Create a PRD from resolved requirements, break it into tracer-bullet implementation issues, and publish via GitHub when available or local files when not.
60tdd-implementation
Test-first implementation discipline for assigned work using a strict red-green-refactor loop.
59