iterative-development
Implement sub-tasks iteratively with user approval between each one. Use when working through a task list with user collaboration.
Best use case
iterative-development is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Implement sub-tasks iteratively with user approval between each one. Use when working through a task list with user collaboration.
Teams using iterative-development should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/iterative-development/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How iterative-development Compares
| Feature / Agent | iterative-development | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Implement sub-tasks iteratively with user approval between each one. Use when working through a task list with user collaboration.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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!!!**
Related Skills
xlsx-to-csv
Convert XLSX spreadsheets (single or multi-sheet) to CSV files you can read and grep. Use whenever you need to process an .xlsx report from Xero, Cryptio, bank exports, or any tool that delivers spreadsheet output.
xero-mcp
Use the Xero MCP server — obtain/refresh OAuth2 bearer tokens, troubleshoot authentication, and pick up other operational notes for working with Xero MCP tools. Use when Xero MCP tools fail with authentication errors, when the bearer token has expired (tokens last ~30 min), before starting any Xero workflow, or for general guidance on Xero MCP usage.
xero-browser
General Xero browser automation notes. Use when automating any Xero page with agent-browser — covers non-standard UI patterns, waiting, and dropdown menus.
test-running
Run tests according to repository guidelines. Use after linting passes, before staging changes.
task-orchestration
Orchestrate the complete development workflow for implementing sub-tasks from a task list. Use for end-to-end feature implementation with quality controls.
task-implementation
Implement a single sub-task from a task list. Use when working on feature development with existing task lists.
task-generation
Generate a detailed task list from a PRP. Use after a PRP is created and ready for implementation planning.
subagent-authoring
Create subagent definitions for Claude Code and OpenCode that delegate to skills. Use when creating new subagents or refactoring existing ones to follow the delegation pattern.
slow-command-running
Pipe long running commands through tee(1) to allow watching output and repeated analyses without rerunning
skill-authoring
Create and maintain Claude Code skills following Anthropic best practices. Use when building new skills, refactoring existing ones, or ensuring skills follow official guidelines for structure, naming, progressive disclosure, and testing.
safe-rm
Safely delete files / directories without asking for permission
prp-generation
Generate a Product Requirements Prompt (PRP) from a feature description. Use when starting work on a new feature.