ryan/stickman
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add unique identifier for test_phase3c_walk_recovery.gd

Browse Source
This commit is contained in:
ryan
2026-09-06 13:09:37 -04:00
parent 1f91f3d2e5
commit 80595a0273
53 changed files with 6806 additions and 471 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.opencode/skills/spec-pipeline/SKILL.md
+15 -17
View File
@@ -1,25 +1,23 @@
---
name: spec-pipeline
description: "Executes the full dev-to-docs pipeline: Developer -> Tester -> Writer."
description: "Lean implementation loop: Architect -> Developer -> User Verification."
---
## What I do
## Execution Logic
I orchestrate a sequential feature implementation and verification pipeline:
1. **Phase 1: Architecture (Optional for small edits)**
- `@architect` defines signatures, node structures, or spec updates in `specs/[feature-name].md`.
- **STOP:** Wait for user approval on design choices before invoking developer.
1. **Architect**: Explores codebase, asks clarifying questions, and drafts the spec. *Waits for user approval before handoff.*
2. **Developer**: Implements the feature based on the spec.
3. **Tester**: Runs full unit test suites; repairs failures if found.
4. **Writer**: After updating README and API docs, review `docs/tech_debt_and_optimizations.md` for formatting consistency and ensure no duplicate entries exist.
2. **Phase 2: Implementation & Engine Validation**
- `@developer` updates code and scenes using targeted diffs/snippets.
- `@developer` runs headless syntax verification:
`& "C:\Godot4\Godot_v4.7.1-stable_win64_console.exe" --headless --check-only --script "res://path/to/script.gd" --path "C:\Godot4\project"`
- If static check fails, `@developer` fixes the code immediately.
## Execution Rules
3. **Phase 3: User Hand-off (Stop)**
- Present the changes to the user to test inside the Godot Editor.
- Do NOT update READMEs or documentation yet.
- **Architect Gate**: Stop after Phase 3 and wait for user approval on the spec before calling `@developer`.
- **Tester Repair Limit**: Allow `@tester` a maximum of 2 auto-repair attempts for failing test suites. If tests still fail after 2 attempts, hand the error context back to `@developer` to fix the underlying implementation.
- Stop and ask the user for clarification if any step fails or is ambiguous.
- Use `@` mentions to trigger subagents sequentially.
- Pass context from each completed stage to the next stage.
## When to use me
Invoke me when you are ready to begin a new feature/fix or when the Architect has finished a specification.
4. **Phase 4: Documentation (Triggered manually by user)**
- Only call `@writer` after the user confirms: _"Feature verified and working."_