Skip to content
cccskills
FreePublished on GitHub

iterative-development

Implements sub-tasks from a task list at .ai/[feature]/tasks.md strictly one at a time, stopping after each to ask the user before starting the next, and keeping the task list and Relevant Files section current. Use when the user wants to review or approve each sub-task before work continues, rather than letting the agent run the list unattended with task-orchestration.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Iterative Development

Implement sub-tasks one at a time with user approval between each.

When to Use This Skill

Use this skill when:

  • Working through a task list (.ai/[feature]/tasks.md)
  • You want user feedback between each sub-task
  • Following a collaborative development workflow

Instructions

Sub-task Implementation

  • Update the task list as you work
  • Add new tasks as they emerge
  • Also update the corresponding prp.txt as appropriate
  • Maintain the "Relevant Files" section:
    • List every file created or modified
    • Give each file a one-line description of its purpose

Sub-task Iteration (IMPORTANT)

ONLY DO ONE SUB-TASK AT A TIME:

  • Only ever include one sub-task on your internal TODO list
    • This is VERY IMPORTANT!
  • Do NOT start or even consider the next sub-task until you ask the user for permission and they say "yes" or "y"

Stop after each sub-task and wait for the user's go-ahead for the next one.

Quality Controls

After completing each sub-task:

  1. Run linters according to repository guidelines
  2. Run tests according to repository guidelines
  3. If linting or testing fails, fix the issues before proceeding
  4. Ask for user approval before moving to the next sub-task

Communication

After each sub-task:

  1. Summarize what was accomplished
  2. Report any issues encountered
  3. Ask for permission to continue with the next sub-task

Workflow

1. Select one sub-task from tasks.md
2. Implement it completely
3. Run linters and tests
4. Report completion
5. Ask: "Ready for the next sub-task?"
6. Wait for "yes" or "y"
7. Repeat until all sub-tasks complete

Follow the above steps EXACTLY!!! NO EXCEPTIONS!!!

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Applies local reliability, viewport, tab-safety, stale-ref, widget, and browser-boundary lessons to every agent-browser automation. Use alongside the upstream agent-browser skill whenever navigating, clicking, filling, testing, extracting, taking screenshots, or debugging any website with agent-browser.

The English summary is being prepared. Showing the original description.

aspiers/ai-config15Updated Oct 9, 2026

Size the agent-browser Chromium window to fill its current screen, leaving a configurable bottom margin for the desktop panel. Use before any agent-browser automation that needs the full screen visible without elements overlapping or scrolling off (e.g. Xero, dense web apps).

The English summary is being prepared. Showing the original description.

aspiers/ai-config15Updated Oct 9, 2026

Create Claude Code slash commands, OpenCode command files, Pi prompt templates, and Codex custom prompts that delegate to the right subagent or skill. Use when creating new commands, porting commands across agent platforms, or refactoring existing commands to follow platform conventions.

The English summary is being prepared. Showing the original description.

aspiers/ai-config15Updated Oct 9, 2026

Adds or changes allowed commands in AI agent permission configs for OpenCode and Claude Code. Use when a command needs adding to an agent's allow list, when permission settings for existing commands need changing, when setting up a new AI tool that requires command permissions, or when the user asks to stop being prompted for a particular command.

The English summary is being prepared. Showing the original description.

aspiers/ai-config15Updated Oct 9, 2026

bc

Free

Creates a Beads issue for a described problem or piece of work without doing the work itself. Use when the user invokes `/bc` or `$bc`, or asks to file, log, or record a bead for something. To also carry out the work, use the `bx` skill instead.

The English summary is being prepared. Showing the original description.

aspiers/ai-config15Updated Oct 9, 2026

bdr

Free

Stores a persistent memory or learning with `bd remember` so it survives across sessions. Use when the user invokes `/bdr` or `$bdr`, or asks to remember, note, or persist an insight in a Beads workspace.

The English summary is being prepared. Showing the original description.

aspiers/ai-config15Updated Oct 9, 2026

See all skills by aspiers

Report a problem with this skill