Skip to content
Skills Library
AI & agents · Automation

feature-loop

/feature-loop

Orchestrate the agent team to take one feature from idea to release-ready - spec-writer, architect, builder, reviewer, security-checker, feature-engineer (if ML), release-docs - with human approval gates. Use when the owner says "run the loop", "build feature X", or gives a new feature idea.

Licence
MIT
Last repository change
04.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Orchestrate the agent team to take one feature from idea to release-ready - spec-writer, architect, builder, reviewer, security-checker, feature-engineer (if ML), release-docs - with human approval gates. Use when the owner says "run the loop", "build feature X", or gives a new feature idea.

Triggers from the description

run the loopbuild feature X
Original author description

Orchestrate the agent team to take one feature from idea to release-ready - spec-writer, architect, builder, reviewer, security-checker, feature-engineer (if ML), release-docs - with human approval gates. Use when the owner says "run the loop", "build feature X", or gives a new feature idea.

How it works

  1. Step by step
  2. Orchestrator rules
Original SKILL.md headings · 52 lines, 529 words
SKILL.md preview
---
name: feature-loop
description: Orchestrate the agent team to take one feature from idea to release-ready - spec-writer, architect, builder, reviewer, security-checker, feature-engineer (if ML), release-docs - with human approval gates. Use when the owner says "run the loop", "build feature X", or gives a new feature idea.
---

# Feature Loop — how the agent team works together

You (the main session) are the **orchestrator**. You assign work to subagents, pass their
outputs forward, and stop at every gate for the human owner. You do not do the specialists' work yourself.

```
Idea ─► [1 spec-writer] ─► GATE A ─► [2 architect] ─► GATE B ─► [3 builder ×N tasks]
     ─► [4 reviewer] ─┬─ changes ─► back to 3 (max 3 rounds, then escalate)
                      └─ approve ─► [5 security-checker] ─► [6 release-docs] ─► GATE C (owner merges/deploys)
              (if the feature needs a model: [ML feature-engineer] runs between 2 and 3)
```

## Step by step

**0. Intake** — Check that `.claude/profiles/product.md` exists and has no `<…>` placeholders; if not, run the `product-setup` skill first. Then restate the idea in one sentence and create a task list with the stages below.

**1. Definition** — Call `spec-writer` with the idea and any evidence.
→ **GATE A (owner):** show the feature card(s), the RICE scores and what was cut.
Ask: "Approve, change, or cut?" Do not continue without a clear approval.

**2. Design** — Call `architect` with the approved card IDs.
→ **GATE B (owner):** show the impact map, risks, any PROPOSED ADR, and the task list.
For a visible change, show the three variants and ask the owner to pick one.
An ADR must be ACCEPTED by the owner before building.

**2b. ML (only if the design says the feature depends on a model)** — Call `feature-engineer`.
If its report says the model does not beat the baseline, bring that to the owner before building.

**3. Build** — For each task in dependency order, call `builder` with ONE task.
Independent tasks may run in parallel. If a builder reports BLOCKED, resolve or escalate — never guess.

**4. Review** — Call `reviewer` with the card and the diff. Do **not** pass the builder's report to the reviewer.
- CHANGES REQUESTED → send blockers/majors back to `builder` as new tasks. Max 3 rounds; then stop and
  tell the owner the task is stuck and why.

**5. Security** — Call `security-checker` when the change touches auth, data, payments, uploads,
external APIs, AI prompts or infra — and always before a release. Any CRITICAL/HIGH → back to step 3.

**6. Release prep** — Call `release-docs`.
→ **GATE C (owner):** present the release package. The owner merges, deploys and publishes. Agents never do —
check the profile's **Three facts** section: if a push deploys, even "just pushing the branch to main" is a release.

**7. After launch (owner + spec-writer, ~1–2 weeks later)** — Compare the success signal to its target.
Decide: keep, iterate, or remove. Write the result into the feature card.

## Orchestrator rules
- One feature per loop. Do not start feature #2 until #1 reaches Gate C, unless the owner says so.
- Keep the owner's view short: at each gate, ≤ 10 lines + links to files.
- Never mark a stage complete because an agent *said* it is done — check the file or the test output.
- Cost control: if a single task takes more than ~3 builder attempts, stop and ask the architect to split it.

Versions

The database has no other skills named feature-loop.

Database snapshot: 13.11.2026 · package version 4be4ab28c3c2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90atdd-team
    Use to orchestrate a team-based ATDD workflow — six phases (spec writing, spec review, pipeline generation, implementation, refine, verify & harden) each handled by a fresh agent so no role erodes across a long-running feature. Triggers — "build a feature with a team", "use ATDD…
  • 90run
    Use to drive one feature from CP2 to CP8 under a coordinator. It proposes the feature's agent graph (shapes, model classes, loop caps, cost estimate), then dispatches every checkpoint as a fresh agent, stopping only at the front and back human gates. Triggers — "/engineer.run…
  • 90implement
    Implement one phase of a feature from its AI-SPEC. Use when the user asks to implement, build or code a feature phase that already has an AI-SPEC in docs/features/<Feature>/.
  • 90starter
    Use when you need to act as the Project Manager orchestrating the agent swarm (Architect, Engineer, Auditor, Product Owner) to drive a feature, bug fix, or refactor through the full spec→plan→execute lifecycle. Load this role before running any operation. Triggers - "be the…
  • 100feature-planning
    Use when the user says \"plan a feature\", \"brainstorm\", \"explore this idea\", or wants to go from idea to structured plan and roadmap.
  • 100loop-architect
    Design well-structured agent loops with best-practice coaching and cross-model review gates before you run them. Use when the user wants to design, build, or set up an agent loop, iterative agent workflow, self-review loop, LLM-as-judge loop, multi-model council, reviewer/judge…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.