bpmn-workflow
Generate and maintain BPMN 2.0 diagrams linked to Gherkin scenarios
Iterate until success or limit, composing existing skills with Jidoka integration
$ npx -y skills add WellApp-ai/Well --skill autonomous-loop --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/autonomous-loopContext preview
The summary Claude sees to decide when to auto-load this skill.
Iterate until success or limit, composing existing skills with Jidoka integration
name: autonomous-loop description: Iterate until success or limit, composing existing skills with Jidoka integration
Keep iterating until success without human intervention per attempt. Composes existing skills and respects Jidoka escalation.
| Param | Default | Description | |-------|---------|-------------| | max_iterations | 5 | Max attempts before pause | | success_criteria | typecheck + lint + ReadLints clean | What defines success |
1. Acknowledge activation 2. Invoke `session-status` skill for current state 3. Initialize counters:
**Output:**
Entering autonomous loop. Max 5 iterations. Current: [session-status header]
FOR iteration IN 1..max_iterations:
2.1: Execute current task action
- Implement changes per commit plan
- Run npm run typecheck
- Run npm run lint
2.2: Invoke pr-review skill
- If BLOCK: proceed to 2.4
- If PASS: proceed to 2.3
2.3: Invoke qa-commit skill
- If GREEN: proceed to 2.5
- If RED: proceed to 2.4
2.4: Invoke debug skill
- Debug skill checks Jidoka tier internally
- If Tier 2/3 escalation: EXIT loop, return JIDOKA
- If Tier 1 fix attempted: CONTINUE loop
2.5: Success checkpoint
- Log iteration as SUCCESS
- Proceed to next commit or EXIT if doneAfter each iteration, output:
## Iteration [N]/[max] | Step | Skill | Result | |------|-------|--------| | Execute | (implementation) | [files changed] | | Review | pr-review | PASS/BLOCK | | Verify | qa-commit | GREEN/RED | | Debug | debug | [if invoked] | **Outcome:** [SUCCESS / CONTINUE / JIDOKA / MAX]
On loop exit, invoke `session-status` skill and output:
## Autonomous Loop Complete **Exit reason:** [SUCCESS / JIDOKA / MAX / INTERRUPT] **Iterations:** [N] of [max] | Iter | Action | Result | |------|--------|--------| | 1 | [description] | [outcome] | | 2 | [description] | [outcome] | [session-status footer with next steps]
| Condition | Trigger | Result | |-----------|---------|--------| | SUCCESS | All checks pass, commit complete | Normal exit, proceed to next commit | | JIDOKA | Tier 2/3 escalation triggered | Exit loop, present options to human | | MAX | iteration >= max_iterations | Exit loop, report and wait for guidance | | INTERRUPT | User sends message | Exit loop, respond to user |
Ralph Wiggum respects Jidoka escalation tiers:
| Tier | Ralph Behavior | |------|----------------| | Tier 1 (error_count < 3) | Continue autonomously, debug skill handles | | Tier 2 (same error 3x) | EXIT loop, Jidoka presents options | | Tier 3 (any error 5x) | EXIT loop, Jidoka requires human triage |
This skill composes:
This skill is invoked by:
Trigger with: "ralph mode", "keep going", "iterate until done"
| Tool | Purpose | |------|---------| | Shell | npm run typecheck, npm run lint | | ReadLints | IDE diagnostic errors | | Grep | Pattern search in code | | SemanticSearch | Find implementations | | Read | Read file contents | | StrReplace | Make code changes | | Browser MCP | Visual verification (via qa-commit) |
Generate and maintain BPMN 2.0 diagrams linked to Gherkin scenarios
Research best-in-class products using Browser MCP and WebSearch
Systematic debugging with MCP integration, auto-invoke from qa-commit, Phase 7 Harden
Capture patine (decision wisdom) at Gates when KO or challenge occurs