Comprehensive developer toolkit providing reusable skills for Java/Spring Boot, TypeScript/NestJS/React/Next.js, Python, PHP, AWS CloudFormation, AI/RAG, DevOps, and more.
90
90%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
This template generates prompt.md for the shell loop approach. One invocation = one step. The LLM reads state, executes one step, updates state, and stops.
Generated by /developer-kit-specs:specs.ralph-loop --action=start.
Ralph Loop State Machine — One Step Per Invocation
================================================
Read fix_plan.json → Execute current step → Update state → Stop
DO NOT execute multiple steps. One step only.
Current State:
- Step: CURRENT_STEP
- Task: CURRENT_TASK (or "none")
- Range: FROM_TASK → TO_TASK
- Iteration: ITERATION_NUM
- Retry count: RETRY_COUNT (for review failures)
Execute Step: CURRENT_STEP
==========================
[Step-specific instructions below]1. Read all task files from SPEC_FOLDER/tasks/TASK-*.md
2. Extract from YAML frontmatter: id, title, status, lang, dependencies, complexity
3. Parse --from-task and --to-task to set task_range
4. Filter tasks by range: exclude tasks with number < from_num or > to_num
5. Set state.step = "choose_task"
6. Save fix_plan.json
7. Print: "Initialized | Range: TASK-036→TASK-041 | Tasks in range: N"1. Read fix_plan.json
2. Filter pending tasks to only those within task_range
3. Filter to tasks where all dependencies are in done array
4. Sort by priority (lower complexity_score = higher priority)
5. If no tasks remain:
- Set state.step = "complete"
- Save and print completion summary
6. Else:
- Pick first task (most important)
- Set state.current_task = TASK-ID
- Set state.current_task_file = task file path
- Set state.current_task_lang = lang
- Set state.step = "implementation"
- Set state.retry_count = 0
7. Save fix_plan.json
8. Print: "Chosen: TASK-ID [title] | Next: implementation"1. Read fix_plan.json to get current_task and current_task_file
2. Read the task file CURRENT_TASK_FILE
3. Run task-implementation:
/specs:task-implementation --lang=LANG --task="TASK_FILE"
4. If implementation succeeds:
- Set state.step = "review"
5. If implementation fails:
- Set state.step = "failed"
- Set state.error = "implementation failed"
6. Save fix_plan.json
7. Print: "Implementation: TASK-ID | Success → review | Failure → failed"1. Read fix_plan.json to get current_task and current_task_file
2. Run task-review with --no-confirm:
/specs:task-review --no-confirm --lang=LANG "TASK_FILE"
3. Read the review report TASK-FILE--review.md
4. If review passes (all criteria met, no issues):
- Set state.step = "cleanup"
5. If review fails (issues found):
- Increment state.retry_count
- If retry_count >= 3:
- Set state.step = "failed"
- Set state.error = "review failed after 3 retries"
- Else:
- Set state.step = "fix"
6. Save fix_plan.json
7. Print: "Review: TASK-ID | Clean → cleanup | Issues → fix (retry N/3)"1. Read fix_plan.json to get current_task and current_task_file
2. Run code-cleanup with --no-confirm:
/specs:code-cleanup --no-confirm --lang=LANG --task="TASK_FILE"
3. Set state.step = "sync"
4. Save fix_plan.json
5. Print: "Cleanup: TASK-ID complete | Next: sync"1. Read fix_plan.json to get current_task
2. Read the review report: docs/specs/[id]/tasks/TASK-XXX--review.md
3. Fix the reported issues:
- Run /specs:task-implementation --lang=LANG --task="TASK_FILE"
- Or manually apply edits to address findings
4. If fixes succeed:
- Set state.step = "review"
5. If fixes fail:
- Set state.step = "failed"
- Set state.error = "fix failed"
6. Save fix_plan.json
7. Print: "Fix: TASK-ID applied | Next: review"1. Read fix_plan.json to get current_task and spec_folder
2. Run spec-sync-with-code:
/specs:spec-sync-with-code SPEC_FOLDER/ --after-task=TASK-ID
3. Set state.step = "update_done"
4. Save fix_plan.json
5. Print: "Sync: TASK-ID complete | Next: update_done"1. Read fix_plan.json to get current_task
2. Update the task's YAML frontmatter:
- status: completed
- completed_date: YYYY-MM-DD
3. In fix_plan.json:
- Move TASK-ID from pending[] to done[]
- Increment state.iteration
- Increment state.range_progress.done_in_range
- Update state.last_updated
- For each remaining pending task: check if all dependencies are in done[], if yes set dependencies_satisfied = true
4. Set state.step = "choose_task"
5. Save fix_plan.json
6. Print: "Done: TASK-ID | Progress: N/M in range (P%) | Next: choose_task"Ralph Loop COMPLETE
=====================
Task Range: FROM_TASK → TO_TASK
Tasks Completed: N/N
Total Iterations: ITERATION_NUM
Deviations Detected: N
All tasks in range implemented and verified.
Run --action=start with a new range to continue.Ralph Loop FAILED
==================
Task: CURRENT_TASK
Error: ERROR_MESSAGE
Retry count: RETRY_COUNT/3
Fix the issues manually, then resume:
/developer-kit-specs:specs.ralph-loop --action=loop --spec=SPEC_FOLDER/init, choose_task, implementation, review, fix, cleanup, sync, update_done, complete, failed. If state.step is anything else, STOP and report a format error.--no-confirm on sub-commands to prevent interactive prompts.Only one thing per loop. One thing per loop.
docs
plugins
developer-kit-ai
developer-kit-aws
agents
docs
skills
aws
aws-cli-beast
aws-cost-optimization
aws-drawio-architecture-diagrams
aws-sam-bootstrap
aws-cloudformation
aws-cloudformation-auto-scaling
aws-cloudformation-bedrock
aws-cloudformation-cloudfront
aws-cloudformation-cloudwatch
aws-cloudformation-dynamodb
aws-cloudformation-ec2
aws-cloudformation-ecs
aws-cloudformation-elasticache
references
aws-cloudformation-iam
references
aws-cloudformation-lambda
aws-cloudformation-rds
aws-cloudformation-s3
aws-cloudformation-security
aws-cloudformation-task-ecs-deploy-gh
aws-cloudformation-vpc
references
developer-kit-core
agents
commands
skills
developer-kit-devops
developer-kit-java
agents
commands
docs
skills
aws-lambda-java-integration
aws-rds-spring-boot-integration
aws-sdk-java-v2-bedrock
aws-sdk-java-v2-core
aws-sdk-java-v2-dynamodb
aws-sdk-java-v2-kms
aws-sdk-java-v2-lambda
aws-sdk-java-v2-messaging
aws-sdk-java-v2-rds
aws-sdk-java-v2-s3
aws-sdk-java-v2-secrets-manager
clean-architecture
graalvm-native-image
langchain4j-ai-services-patterns
references
langchain4j-mcp-server-patterns
references
langchain4j-rag-implementation-patterns
references
langchain4j-spring-boot-integration
langchain4j-testing-strategies
langchain4j-tool-function-calling-patterns
langchain4j-vector-stores-configuration
references
qdrant
references
spring-ai-mcp-server-patterns
spring-boot-actuator
spring-boot-cache
spring-boot-crud-patterns
spring-boot-dependency-injection
spring-boot-event-driven-patterns
spring-boot-openapi-documentation
spring-boot-project-creator
spring-boot-resilience4j
spring-boot-rest-api-standards
spring-boot-saga-pattern
spring-boot-security-jwt
assets
references
scripts
spring-boot-test-patterns
spring-data-jpa
references
spring-data-neo4j
references
unit-test-application-events
unit-test-bean-validation
unit-test-boundary-conditions
unit-test-caching
unit-test-config-properties
references
unit-test-controller-layer
unit-test-exception-handler
references
unit-test-json-serialization
unit-test-mapper-converter
references
unit-test-parameterized
unit-test-scheduled-async
references
unit-test-service-layer
references
unit-test-utility-methods
unit-test-wiremock-rest-api
references
developer-kit-php
developer-kit-project-management
developer-kit-python
developer-kit-specs
commands
docs
hooks
test-templates
tests
skills
developer-kit-tools
developer-kit-typescript
agents
docs
hooks
rules
skills
aws-cdk
aws-lambda-typescript-integration
better-auth
clean-architecture
drizzle-orm-patterns
dynamodb-toolbox-patterns
references
nestjs
nestjs-best-practices
nestjs-code-review
nestjs-drizzle-crud-generator
nextjs-app-router
nextjs-authentication
nextjs-code-review
nextjs-data-fetching
nextjs-deployment
nextjs-performance
nx-monorepo
react-code-review
react-patterns
shadcn-ui
tailwind-css-patterns
tailwind-design-system
references
turborepo-monorepo
typescript-docs
typescript-security-review
zod-validation-utilities
references
github-spec-kit