Implement
sickn33/agentic-awesome-skills
Implement a piece of work based on a PRD or set of issues. An agent skill from sickn33/agentic-awesome-skills.
Sequences a substantial change through the ideate/design/implement/ review/document loop, checkpointing with self-review after every step and looping back when one fails.
Apache-2.0Auto-check passed
Install Running A Development Iteration
$ npx skills add agntcy/coffeeAgntcy --skill running-a-development-iteration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install agntcy/coffeeAgntcy running-a-development-iteration --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/agntcy/coffeeAgntcy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/process/running-a-development-iteration .claude/skills/running-a-development-iteration && 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 "running-a-development-iteration" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/process/running-a-development-iteration into .claude/skills/running-a-development-iteration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "running-a-development-iteration", 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/agntcy/coffeeAgntcy/tree/main/.agents/skills/process/running-a-development-iterationType 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 agntcy/coffeeAgntcy --skill running-a-development-iteration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install agntcy/coffeeAgntcy running-a-development-iteration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/process/running-a-development-iteration .agents/skills/running-a-development-iteration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "running-a-development-iteration" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/process/running-a-development-iteration into .agents/skills/running-a-development-iteration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "running-a-development-iteration", 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 agntcy/coffeeAgntcy --skill running-a-development-iteration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install agntcy/coffeeAgntcy running-a-development-iteration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/process/running-a-development-iteration .cursor/skills/running-a-development-iteration && 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 "running-a-development-iteration" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/process/running-a-development-iteration into .cursor/skills/running-a-development-iteration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "running-a-development-iteration", 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/agntcy/coffeeAgntcy.git --path .agents/skills/process/running-a-development-iteration--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 agntcy/coffeeAgntcy --skill running-a-development-iteration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install agntcy/coffeeAgntcy running-a-development-iteration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/process/running-a-development-iteration .gemini/skills/running-a-development-iteration && 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 "running-a-development-iteration" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/process/running-a-development-iteration into .gemini/skills/running-a-development-iteration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "running-a-development-iteration", 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 agntcy/coffeeAgntcy running-a-development-iterationInstalls 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 agntcy/coffeeAgntcy --skill running-a-development-iteration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/process/running-a-development-iteration .github/skills/running-a-development-iteration && 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 "running-a-development-iteration" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/process/running-a-development-iteration into .github/skills/running-a-development-iteration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "running-a-development-iteration", 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 agntcy/coffeeAgntcy --skill running-a-development-iteration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install agntcy/coffeeAgntcy running-a-development-iteration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/process/running-a-development-iteration .opencode/skills/running-a-development-iteration && 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 "running-a-development-iteration" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/process/running-a-development-iteration into .opencode/skills/running-a-development-iteration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "running-a-development-iteration", 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
running-a-development-iteration- GitHub stars
- 112
- Token cost
- ~915 tokens
- SKILL.md length
- 173 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Sequences a substantial change through the ideate/design/implement/ review/document loop, checkpointing with self-review after every step and looping back when one fails.
- Continuing a substantial change (the same threshold plan-with-openspec uses)
- SKILL.md covers What this skill does, Workflow and Notes
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Running A Development Iteration is an agent skill from agntcy/coffeeAgntcy. Sequences a substantial change through the ideate/design/implement/ review/document loop, checkpointing with self-review after every step and looping back when one fails. Use when starting or continuing a substantial change (the same threshold plan-with-openspec uses).
Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: End-to-end reference application for AGNTCY Components. The licence is Apache-2.0.
When your agent uses it
- Continuing a substantial change (the same threshold plan-with-openspec uses)
Example prompts
- “Use the running-a-development-iteration skill to sequence a substantial change through the ideate/design/implement/ review/document loop…”
- “/running-a-development-iteration”
What it can do on your machine
Read from SKILL.md and the folder at commit 78f588c. 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
Running A Development Iteration loads about 915 tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 173 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 agntcy/coffeeAgntcy at commit 78f588c, republished under its Apache-2.0 licence (© agntcy). 173 words, ~915 tokens.
Download SKILL.mdSave it as
.claude/skills/running-a-development-iteration/SKILL.md (or your agent's skills folder).- name
- running-a-development-iteration
- description
- Sequences a substantial change through the ideate/design/implement/ review/document loop, checkpointing with self-review after every step and looping back when one fails. Use when starting or continuing a substantial change (the same threshold plan-with-openspec uses).
Running a development iteration
What this skill does
Sequences and checkpoints the five-step loop
.agents/rules/process/development-iteration-loop.md
requires for a substantial change. It delegates every step's actual
content to the rule/skill that already owns it - this skill only decides
what runs next and when to loop back.
Workflow
- [ ] 1. Ideate - if the idea isn't concrete yet, work it through the
openspec-explore skill until it is.
- [ ] 2. Design - invoke the openspec-propose skill (proposal, design,
spec delta, tasks).
- [ ] 3. Review the design - before treating design as done, check it
against self-review-after-change's five checks (mainly
"requirements" and "common practices" apply pre-code; give
"repo consistency"/"rule compliance"/"general integrity" a first
pass here too). Note anything documentation-relevant that
surfaces, as a running note in the proposal/design text - don't
wait until step 6 to start tracking it. If review finds a
problem, fix it and re-review before continuing (loop back to 1
or 2 as needed).
- [ ] 4. Implement - invoke the openspec-apply-change skill, working
through tasks.md. Add automated tests for each code change in the
same task, unless infeasible (judgment call - see the rule).
Keep appending documentation-relevant notes as they surface.
- [ ] 5. Review the implementation - run self-review-after-change's full
five checks against the change as it now stands, plus
pre-finalize-checks' applicable automated checks. If review finds
a problem, loop back to whichever step owns it (1, 2, or 4),
fix it, and re-review before continuing.
- [ ] 6. Document - run keep-docs-consistent's full documentation-surface
sweep, reconciling it against the notes accumulated since step 1
- not reconstructing from scratch. Review this step too: if it
surfaces a problem, loop back the same way as any other step.
- [ ] 7. Once the PR merges, invoke the openspec-archive-change skill.Notes
- This skill sequences and checkpoints only - it never restates what
openspec-explore,openspec-propose,openspec-apply-change,self-review-after-change,keep-docs-consistent, oropenspec-archive-changethemselves require. Read each for its own content. - The loop-back clause is not optional under time pressure: a review finding at any step, including the last one, sends the change back to fix the step that owns it, then re-reviews before continuing.
- "Documentation notes start at step 1" has no separate file or format - for an OpenSpec-tracked change, the proposal/design text itself is where these notes live, since both already get written and revised starting at the design step, and ideate's own exploration can note documentation implications inline before a proposal even exists.
- See
.agents/rules/process/development-iteration-loop.mdfor the underlying rule, and.agents/rules/process/plan-with-openspec.mdfor the substantial-change threshold this skill's trigger reuses.
© agntcy, Apache-2.0. 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 .agents/skills/process/running-a-development-iteration of agntcy/coffeeAgntcy.
Open the folder on GitHubat commit 78f588c
Compare with similar skills
Running A Development Iteration 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 |
|---|---|---|---|---|---|---|
| Running A Development Iteration this skillagntcy/coffeeAgntcy | 112 | — | ~915 | Automated safety check: Pass | Apache-2.0 | |
| Implementsickn33/agentic-awesome-skills | 47k | 5 repos | ~306 | Automated safety check: Pass | MIT | |
| Implementcodewhale-hq/Codewhale | 41k | — | ~190 | Automated safety check: Pass | MIT | |
| Incremental Implementationaddyosmani/agent-skills | 104k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Implementbestofjs/bestofjs | 3.1k | 18 repos | ~109 | Automated safety check: Pass | MIT | |
| ImplementAutomattic/simplenote-android | 1.9k | — | ~1.1k | Automated safety check: Pass | GPL-2.0 |
Similar skills
Implement
codewhale-hq/Codewhale
Carry an authorized, defined request or approved plan through scoped edits and proportionate verification.
Incremental Implementation
addyosmani/agent-skills
Delivers a change in thin vertical slices, each implemented, tested, verified and committed before the next, using vertical, contract-first or risk-first slicing.
Implement
bestofjs/bestofjs
Implement a piece of work based on a spec or set of tickets.
Implement
Automattic/simplenote-android
End-to-end implementation workflow: plan, implement, verify, commit, and open a draft PR.
Sparc Implement
ruvnet/ruflo
Run the SPARC Pseudocode and Architecture phases (2 and 3) — write algorithm pseudocode, design module boundaries and API contracts, then implement
More from agntcy/coffeeAgntcy
All 20 skills in this repoA2a Protocol
agntcy/coffeeAgntcy
A skill your agent uses when the user asks about A2A (Agent-to-Agent) protocol communication, OASF record formats, AGNTCY directory operations, agent card parsing, or dirctl CLI usage.
Add Repo Operation
agntcy/coffeeAgntcy
Guides adding a new repository operation (a check, validation, or piece of tooling) through this repo's standard script - Taskfile task - skill - CI enforcement - rule pipeline.
Agentic Workflows API Documentation Lungo
agntcy/coffeeAgntcy
Authors and maintains the human-facing Agentic Workflows API documentation for the lungo subproject at coffeeAGNTCY/coffeeagents/lungo/docs/workflow-instanceapi.md.
Checking Helm Chart Version Bumps
agntcy/coffeeAgntcy
Checks whether any Helm chart under coffeeAGNTCY/coffeeagents/{corto,lungo}/deployment/helm// has content changes not covered by a later Chart.yaml version: bump, anywhere in that chart's history…
Checking Pinned References
agntcy/coffeeAgntcy
Runs task pins:check to find any third-party GitHub Action, reusable-workflow, or image reference that isn't pinned to an immutable SHA/digest, and pins each one it finds.
Checking Workflow Permissions
agntcy/coffeeAgntcy
Runs task workflows:check-permissions to find any GitHub Actions workflow file with a write-all grant or no declared permissions, and scopes it down to least privilege.
Questions about Running A Development Iteration
What does Running A Development Iteration do?
Sequences a substantial change through the ideate/design/implement/ review/document loop, checkpointing with self-review after every step and looping back when one fails. Running A Development Iteration is an agent skill from agntcy/coffeeAgntcy. Sequences a substantial change through the ideate/design/implement/ review/document loop, checkpointing with self-review after every step and looping back when one fails.
When should I use Running A Development Iteration?
Running A Development Iteration fits situations like: continuing a substantial change (the same threshold plan-with-openspec uses).
How do I install Running A Development Iteration in Claude Code?
Run `npx skills add agntcy/coffeeAgntcy --skill running-a-development-iteration -a claude-code`. Or copy the skill folder (.agents/skills/process/running-a-development-iteration in agntcy/coffeeAgntcy) into .claude/skills/running-a-development-iteration in your project. Claude Code loads it when a task matches its description.
How do I install Running A Development Iteration in Codex?
Run `npx skills add agntcy/coffeeAgntcy --skill running-a-development-iteration -a codex`. Or copy the skill folder (.agents/skills/process/running-a-development-iteration in agntcy/coffeeAgntcy) into .agents/skills/running-a-development-iteration in your project. Codex loads it when a task matches its description.
Can I use Running A Development Iteration 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 agntcy/coffeeAgntcy --skill running-a-development-iteration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/running-a-development-iteration, .gemini/skills/running-a-development-iteration, .github/skills/running-a-development-iteration and .opencode/skills/running-a-development-iteration in your project.
What does Running A Development Iteration need to run?
SKILL.md names no scripts, command-line tools or credentials: Running A Development Iteration is instructions for the agent only.
Does Running A Development Iteration 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 Running A Development Iteration 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 Running A Development Iteration use?
Running A Development Iteration is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Running A Development Iteration use?
About 915 tokens (SKILL.md is roughly 3.7k 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 Running A Development Iteration?
Skills that share tags, products or a category with Running A Development Iteration: Implement (sickn33/agentic-awesome-skills, 47k stars), Implement (codewhale-hq/Codewhale, 41k stars), Incremental Implementation (addyosmani/agent-skills, 104k stars) and Implement (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Running A Development Iteration?
agntcy (a GitHub organization) maintains it in agntcy/coffeeAgntcy, which has 112 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 9, 2026.
Source: agntcy/coffeeAgntcy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.