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.
Spec-writing stage skill for the architect factory: synthesizes the run's conversation, repo evidence, and research findings into docs/spec/<run.md after grounding.
Install To Spec
$ npx skills add DanMcInerney/architect-loop --skill to-spec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install DanMcInerney/architect-loop to-spec --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-spec .claude/skills/to-spec && 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-spec" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/to-spec into .claude/skills/to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-spec", 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-specType 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-spec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install DanMcInerney/architect-loop to-spec --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-spec .agents/skills/to-spec && 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-spec" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/to-spec into .agents/skills/to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-spec", 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-spec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install DanMcInerney/architect-loop to-spec --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-spec .cursor/skills/to-spec && 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-spec" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/to-spec into .cursor/skills/to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-spec", 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-spec--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-spec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install DanMcInerney/architect-loop to-spec --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-spec .gemini/skills/to-spec && 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-spec" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/to-spec into .gemini/skills/to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-spec", 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-specInstalls 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-spec -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-spec .github/skills/to-spec && 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-spec" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/to-spec into .github/skills/to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-spec", 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-spec -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-spec --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-spec .opencode/skills/to-spec && 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-spec" agent skill from https://github.com/DanMcInerney/architect-loop/tree/main/skills/to-spec into .opencode/skills/to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-spec", 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-spec- GitHub stars
- 626
- Token cost
- ~956 tokens
- SKILL.md length
- 457 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Spec-writing stage skill for the architect factory: synthesizes the run's conversation, repo evidence, and research findings into docs/spec/<run.md after grounding.
- Works in 5 steps: Read the codebase-design → Name the seam(s) this run will exercise… → Do not include specific file paths or… → …
- Tasks that involve Subagents
- SKILL.md covers Process and Template
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
To Spec is an agent skill from DanMcInerney/architect-loop. Spec-writing stage skill for the architect factory: synthesizes the run's conversation, repo evidence, and research findings into docs/spec/<run.md after grounding. Invoked by the strategist subagent the orchestrator dispatches during /architect intake — or directly by the orchestrator in /architect-fast (that skill's stage-skill deltas apply) — before decomposition into issues.
Its SKILL.md is about 960 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
- Tasks that involve Subagents
Example prompts
- “/to-spec”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read the codebase-design
- Name the seam(s) this run will exercise before drafting any section.
- Do not include specific file paths or code snippets in the spec body —
- Never run the timed-ruling protocol yourself or wait on the human
- Shape the spec on the template below and write it to
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 Spec loads about 956 tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 457 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). 457 words, ~956 tokens.
Download SKILL.mdSave it as
.claude/skills/to-spec/SKILL.md (or your agent's skills folder).- name
- to-spec
- description
- Spec-writing stage skill for the architect factory: synthesizes the run's conversation, repo evidence, and research findings into `docs/spec/<run>.md` after grounding. Invoked by the strategist subagent the orchestrator dispatches during `/architect` intake — or directly by the orchestrator in `/architect-fast` (that skill's stage-skill deltas apply) — before decomposition into issues.
<!-- Adapted from mattpocock/skills (MIT). -->To Spec
Synthesize the spec from what grounding, intake, and research evidence already surfaced; do not interview. Anything genuinely unanswered goes through step 4.
Process
- Read the codebase-design
vocabulary (
skills/codebase-design/SKILL.md) before writing a line. Reuse its module, interface, seam, adapter, depth, and locality terms exactly; never substitute component, service, boundary, or API for module or interface. - Name the seam(s) this run will exercise before drafting any section.
Existing seams are preferred to new ones, at the highest point possible;
the ideal number is one. Record them under
## Implementation decisions. - Do not include specific file paths or code snippets in the spec body — they may end up being outdated very quickly. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts.
- Never run the timed-ruling protocol yourself or wait on the human:
return every open question to the orchestrator, one line each —
RULING NEEDED: <question> | options: <a | b> | default: <option> — <why>— and it runs the protocol (skills/architect/SKILL.md## Timed-ruling protocol). Rulings already present in your dispatch context are decided; record each as an## Assumptionsentry. (Direct orchestrator invocation only —/architect-fast: run the protocol yourself as that lane records.) - Shape the spec on the template below and write it to
docs/spec/<run>.mdin your working tree. Do NOT commit it and do NOT create or update the tracking issue — the spec commit and the tracking-issue update (spec pointer, assumptions digest, or the markdown-mode equivalent inskills/architect/tracker.md## Command mapping) are orchestrator actions after you return. End your reply withSPEC DRAFT: <path>plus anyRULING NEEDED:lines.
Show full SKILL.md (169 more words)Show less
Template
Write the sections below in this order; the names are load-bearing for hardening and decomposition, so keep them exact.
## Goal— what the run adds and why, from the reader's side.## Target flow(optional) — a short numbered sequence, only when the run reorders or replaces a multi-step process; omit for additive or single-surface runs.## Non-goals— what the run deliberately leaves unchanged.## Assumptions— every timed-ruling default this run applied, one line each, dated.## Implementation decisions— modules, interfaces, and the seam(s) from step 2, described, never pathed; the one place a prototype snippet may appear, per step 3.## Validation strategy— how the run's own checks and the closing review confirm the seam(s) hold; name the check-runner and closing review, never new grading machinery.## Domain language— new or changed vocabulary this run introduces, defined once.## Open human decisions— anything unresolved once the timed-ruling protocol's timer expires; empty at freeze.## Verified facts— every claim sourced outside this conversation: source, date fetched, fact supported.## Preflight evidence— tool, auth, and repo-state evidence gathered before decomposition.
© 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-spec of DanMcInerney/architect-loop.
Open the folder on GitHubat commit 28dca7d
Compare with similar skills
To Spec 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 Spec this skillDanMcInerney/architect-loop | 626 | — | ~956 | Automated safety check: Pass | MIT | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 38k | 7 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 37 repos | ~1.2k | Automated safety check: Pass | None | |
| Dispatching Parallel Agentsultralisp/ultralisp | 258 | 40 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 Spec
What does To Spec do?
Spec-writing stage skill for the architect factory: synthesizes the run's conversation, repo evidence, and research findings into docs/spec/<run.md after grounding. To Spec is an agent skill from DanMcInerney/architect-loop.md after grounding.
When should I use To Spec?
To Spec fits situations like: tasks that involve Subagents.
How do I install To Spec in Claude Code?
Run `npx skills add DanMcInerney/architect-loop --skill to-spec -a claude-code`. Or copy the skill folder (skills/to-spec in DanMcInerney/architect-loop) into .claude/skills/to-spec in your project. Claude Code loads it when a task matches its description.
How do I install To Spec in Codex?
Run `npx skills add DanMcInerney/architect-loop --skill to-spec -a codex`. Or copy the skill folder (skills/to-spec in DanMcInerney/architect-loop) into .agents/skills/to-spec in your project. Codex loads it when a task matches its description.
Can I use To Spec 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-spec -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-spec, .gemini/skills/to-spec, .github/skills/to-spec and .opencode/skills/to-spec in your project.
What does To Spec need to run?
SKILL.md names no scripts, command-line tools or credentials: To Spec is instructions for the agent only.
Does To Spec 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 Spec 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 Spec use?
To Spec 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 Spec use?
About 956 tokens (SKILL.md is roughly 3.8k 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 Spec?
Skills that share tags, products or a category with To Spec: 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 Spec?
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.