aspiers/iterative-development
.agents/skills/iterative-development/SKILL.md
Implement sub-tasks iteratively with user approval between each one. Use when working through a task list with user collaboration.
$ install --global
skillsauthnpx skillsauth add aspiers/ai-config iterative-developmentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:50 PM1.8s1 file scanned
SKILL.md
- name:
- iterative-development
- description:
- Implement sub-tasks iteratively with user approval between each one. Use when working through a task list with user collaboration.
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.txtas 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:
- Run linters according to repository guidelines
- Run tests according to repository guidelines
- If linting or testing fails, fix the issues before proceeding
- Ask for user approval before moving to the next sub-task
Communication
After each sub-task:
- Summarize what was accomplished
- Report any issues encountered
- 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
aspiers/test-running
development
VerifiedTrustedCommunity
Run tests according to repository guidelines. Use after linting passes, before staging changes.
9SKILL.mdUpdated Apr 17, 2026
aspiers/task-orchestration
development
VerifiedTrustedCommunity
Orchestrate the complete development workflow for implementing sub-tasks from a task list. Use for end-to-end feature implementation with quality controls.
9SKILL.mdUpdated Apr 17, 2026
aspiers/task-implementation
development
VerifiedTrustedCommunity
Implement a single sub-task from a task list. Use when working on feature development with existing task lists.
9SKILL.mdUpdated Apr 17, 2026
aspiers/task-generation
data-ai
VerifiedTrustedCommunity
Generate a detailed task list from a PRP. Use after a PRP is created and ready for implementation planning.
9SKILL.mdUpdated Apr 17, 2026