Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
A skill your agent uses when decomposing a hardened spec into tracker issues: cutting tracer-bullet vertical slices through every layer, ordering structural work first with blocking edges…
Install To Issues
$ npx skills add DanMcInerney/architect-loop --skill to-issues -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install DanMcInerney/architect-loop to-issues --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/DanMcInerney/architect-loop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/to-issues .claude/skills/to-issues && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "to-issues" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/to-issues into .claude/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/DanMcInerney/architect-loop/tree/main/skills/to-issuesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add DanMcInerney/architect-loop --skill to-issues -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install DanMcInerney/architect-loop to-issues --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DanMcInerney/architect-loop.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/to-issues .agents/skills/to-issues && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "to-issues" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/to-issues into .agents/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DanMcInerney/architect-loop --skill to-issues -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install DanMcInerney/architect-loop to-issues --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DanMcInerney/architect-loop.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/to-issues .cursor/skills/to-issues && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "to-issues" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/to-issues into .cursor/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/DanMcInerney/architect-loop.git --path skills/to-issues--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add DanMcInerney/architect-loop --skill to-issues -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install DanMcInerney/architect-loop to-issues --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DanMcInerney/architect-loop.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/to-issues .gemini/skills/to-issues && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "to-issues" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/to-issues into .gemini/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install DanMcInerney/architect-loop to-issuesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add DanMcInerney/architect-loop --skill to-issues -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/DanMcInerney/architect-loop.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/to-issues .github/skills/to-issues && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "to-issues" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/to-issues into .github/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DanMcInerney/architect-loop --skill to-issues -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install DanMcInerney/architect-loop to-issues --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DanMcInerney/architect-loop.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/to-issues .opencode/skills/to-issues && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "to-issues" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/to-issues into .opencode/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
to-issues- GitHub stars
- 626
- Token cost
- ~1.2k tokens
- SKILL.md length
- 614 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when decomposing a hardened spec into tracker issues: cutting tracer-bullet vertical slices through every layer, ordering structural work first with blocking edges…
- Works in 7 steps: Read before you cut → Structural before behavioral → Cut tracer-bullet vertical slices → …
- Decomposing a hardened spec into tracker issues: cutting tracer-bullet vertical slices through every layer
- SKILL.md covers 1. Read before you cut, 2. Structural before behavioral, 3. Cut tracer-bullet vertical… and 4. Maximize the disjoint…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
To Issues is an agent skill from DanMcInerney/architect-loop. Use when decomposing a hardened spec into tracker issues: cutting tracer-bullet vertical slices through every layer, ordering structural work first with blocking edges, maximizing the disjoint parallel frontier, publishing producer/consumer interface contracts, and attaching a compact change-skeleton to each issue. Invoked only from an explicit architect dispatch — by the harden strategist subagent in /architect, or directly by the orchestrator in /architect-fast — after the spec is written; never left to…
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Subagents. The repository describes itself as: Super optimized /goal loop. Massive token savings and higher quality. Smart model designs and reviews, cheaper model builds.. The licence is MIT.
When your agent uses it
- Decomposing a hardened spec into tracker issues: cutting tracer-bullet vertical slices through every layer
- Ordering structural work first with blocking edges
- Maximizing the disjoint parallel frontier
- Publishing producer/consumer interface contracts
Example prompts
- “/to-issues”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 28dca7d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
To Issues loads about 1.2k tokens when it runs. Until then it costs about 139 tokens; SKILL.md has 614 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from DanMcInerney/architect-loop at commit 28dca7d, republished under its MIT licence (© DanMcInerney). 614 words, ~1,220 tokens.
Download SKILL.mdSave it as
.claude/skills/to-issues/SKILL.md (or your agent's skills folder).- name
- to-issues
- description
- Use when decomposing a hardened spec into tracker issues: cutting tracer-bullet vertical slices through every layer, ordering structural work first with blocking edges, maximizing the disjoint parallel frontier, publishing producer/consumer interface contracts, and attaching a compact change-skeleton to each issue. Invoked only from an explicit architect dispatch — by the harden strategist subagent in `/architect`, or directly by the orchestrator in `/architect-fast` — after the spec is written; never left to description-trigger discovery.
<!-- Adapted from mattpocock/skills (MIT). -->To Issues
Turn the hardened spec into dispatch-ready issues under the tracking issue. The spec already settles the whole plan — this stage does not quiz the human; a hard stop or an oddity escalation is the only thing that opens a question here.
1. Read before you cut
Load the spec, then hold the codebase-design vocabulary
(skills/codebase-design/SKILL.md) exactly: module, interface, implementation, seam, adapter, depth, leverage,
locality for design; run, tracking issue, issue, slice, frozen check,
check-runner, strategist, builder, orchestrator, factory branch, worktree,
job report, verdict, ruling, digest, hard stop for the factory. Never
substitute component/service/boundary/API for module/interface, or
task/ticket for issue — that drift is a defect, not a style choice.
Look for prefactoring while you read: make the change easy, then make the easy change.
2. Structural before behavioral
Structural (prefactoring) issues land first, with blocking edges into the behavioral issues they unblock. A structural issue's checks prove existing behavior stays green — it changes shape, not outcome.
Oddity rule while scoping: a local wart gets a local patch note, not its own issue. A variation that recurs gets a structural issue blocking the behavioral one. One adapter is a hypothetical seam; two adapters make it real — write the structural issue. Three failed fixes on the same point means stop and escalate the design question instead of cutting a fourth fix.
3. Cut tracer-bullet vertical slices
Each issue is a tracer-bullet vertical slice: a narrow but complete path through every layer the change touches, demoable or verifiable on its own — never a horizontal slice of one layer.
Avoid specific file paths or code snippets in issue prose — they go stale fast. Exception: a prototype snippet that encodes a decision more precisely than prose can (state machine, schema, type shape); trim to the decision-rich parts.
4. Maximize the disjoint parallel frontier
Compute readiness from each issue's file-touch set, not only its blocking edges. Issues dispatched in the same wave share no files, migrations, lockfiles, generated artifacts, config, schemas, or other mutable runtime state. A shared-file collision is a decomposition failure — split or resequence; never hand-merge it later.
5. Interface contracts, not future-code citations
An issue that produces a surface another issue consumes publishes an interface contract block: names, parameters, return types, and behavior. Consumer issues cite that block; they never cite the producer's not-yet-written implementation.
Show full SKILL.md (233 more words)Show less
6. Body shape
Every issue carries: acceptance criteria; MAY TOUCH / MUST NOT TOUCH file
sets; its check path; its raw job-report path; blocked-by and parent edges;
a compact change-skeleton (≤30 lines — files, signatures, data flow,
invariants; a contract, not a line mandate). Keep the linked check's RUN
dependencies (the test files, validators, and scripts its commands execute)
out of MAY TOUCH unless the issue explicitly owns them; when it does, name
them in the body as check dependencies. Close every issue body with the
run marker comment: <!-- architect-run: <run> -->.
7. Draft in publish order; the orchestrator publishes
Write one draft file per issue at docs/runs/<run>/issues/<NN>-<slice>.md
(a local run artifact), NN numbered in publish order: structural issues
first, blockers before the issues that cite them. Name blocked-by and
parent edges by slice name — real issue numbers do not exist yet; the
orchestrator maps slice names to issue numbers as it publishes in NN
order, so every blocked-by resolves to a real, already-open issue and
never a forward reference. Do not post to the tracker yourself —
publishing sub-issues, edges, and claims are orchestrator actions
(skills/architect/dispatch.md ## Issue conventions). When the
orchestrator runs this skill directly (/architect-fast), it publishes
the drafts itself in the same order.
Done when every slice in the plan has a draft file — structural-first,
frontier-maxed — whose order publishes with no forward references. End
your reply with one line: ISSUE DRAFTS: <count> at docs/runs/<run>/issues/.
© DanMcInerney, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/to-issues of DanMcInerney/architect-loop.
Open the folder on GitHubat commit 28dca7d
Compare with similar skills
To Issues next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| To Issues this skillDanMcInerney/architect-loop | 626 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 38k | 8 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 38 repos | ~1.2k | Automated safety check: Pass | None | |
| Dispatching Parallel Agentsultralisp/ultralisp | 258 | 41 repos | ~1.5k | Automated safety check: Pass | None | |
| Paseo Advisor Second Opiniongetpaseo/paseo | 20k | 1 repos | ~756 | Automated safety check: Pass | Custom licence | |
| Task Observerrebelytics/one-skill-to-rule-them-all | 3.2k | 1 repos | ~12k | Automated safety check: Pass | CC-BY-4.0 |
Similar skills
- Official
Subagent Driven Development
Asvarox/allkaraoke
A skill your agent uses when executing implementation plans with independent tasks in the current session
Dispatching Parallel Agents
ultralisp/ultralisp
A skill your agent uses when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Paseo Advisor Second Opinion
getpaseo/paseo
Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.
Task Observer
rebelytics/one-skill-to-rule-them-all
Monitors task execution for skill improvement opportunities.
O2 Review Loop
openobserve/openobserve
Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.
More from DanMcInerney/architect-loop
All 11 skills in this repoArchitect Research
DanMcInerney/architect-loop
A skill your agent uses when the user asks for discovery-scale research that informs a decision: brainstorming a project or feature, choosing a technology, or requests like "research X", "what's the…
Adversarial Review
DanMcInerney/architect-loop
A skill your agent uses when the architect factory orchestrator dispatches a fresh strategist subagent to harden a draft spec: falsify it with file:line evidence, fold the surviving findings into a…
Architect
DanMcInerney/architect-loop
A skill your agent uses when the user asks to architect, run or continue the autonomous software factory, turn a goal into a hardened tracker issue plan, dispatch builder jobs, grade finished work…
Architect Fast
DanMcInerney/architect-loop
A skill your agent uses when the user asks to architect-fast a change, run the light factory lane, or factory-build a small goal — a few files, roughly one sitting, at most ~3 parallel issues — into…
Final Review
DanMcInerney/architect-loop
A skill your agent uses for the closing whole-run review in the architect factory — the only model review in the loop: dispatched by the orchestrator, at finish, to one fresh strategist subagent…
Frozen Checks
DanMcInerney/architect-loop
A skill your agent uses when the strategist drafts per-issue graded checks after decomposition and before builder dispatch.
Related
Categories
Questions about To Issues
What does To Issues do?
A skill your agent uses when decomposing a hardened spec into tracker issues: cutting tracer-bullet vertical slices through every layer, ordering structural work first with blocking edges…. To Issues is an agent skill from DanMcInerney/architect-loop. Use when decomposing a hardened spec into tracker issues: cutting tracer-bullet vertical slices through every layer, ordering structural work first with blocking edges, maximizing the disjoint parallel frontier, publishing producer/consumer interface contracts, and attaching a compact change-skeleton to each issue.
When should I use To Issues?
To Issues fits situations like: decomposing a hardened spec into tracker issues: cutting tracer-bullet vertical slices through every layer; ordering structural work first with blocking edges; maximizing the disjoint parallel frontier; publishing producer/consumer interface contracts.
How do I install To Issues in Claude Code?
Run `npx skills add DanMcInerney/architect-loop --skill to-issues -a claude-code`. Or copy the skill folder (skills/to-issues in DanMcInerney/architect-loop) into .claude/skills/to-issues in your project. Claude Code loads it when a task matches its description.
How do I install To Issues in Codex?
Run `npx skills add DanMcInerney/architect-loop --skill to-issues -a codex`. Or copy the skill folder (skills/to-issues in DanMcInerney/architect-loop) into .agents/skills/to-issues in your project. Codex loads it when a task matches its description.
Can I use To Issues in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add DanMcInerney/architect-loop --skill to-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/to-issues, .gemini/skills/to-issues, .github/skills/to-issues and .opencode/skills/to-issues in your project.
What does To Issues need to run?
SKILL.md names no scripts, command-line tools or credentials: To Issues is instructions for the agent only.
Does To Issues access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is To Issues safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does To Issues use?
To Issues is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does To Issues use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to To Issues?
Skills that share tags, products or a category with To Issues: Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Subagent Driven Development (Asvarox/allkaraoke, 261 stars), Dispatching Parallel Agents (ultralisp/ultralisp, 258 stars) and Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains To Issues?
DanMcInerney (a GitHub user) maintains it in DanMcInerney/architect-loop, which has 626 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 13, 2026.
Source: DanMcInerney/architect-loop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.