ryan
e3df1cc5c0
- Added KINEMATIC_BLENDING_AND_RECOVERY.md to outline features for smooth transitions between kinematic and ragdoll states, including visual and physical blending, and ragdoll recovery. - Introduced KINEMATIC_TO_RAGDOLL.md detailing the objectives, scope, and core architecture for transitioning the stickman from kinematic to ragdoll mode. - Created KINEMATIC_TO_RAGDOLL_SPEC.md as an implementation specification, verifying codebase facts and correcting the initial plan based on Godot 4.4 source. - Enhanced StickmanRig with state management for animated and ragdoll modes, including momentum preservation and ragdoll construction. - Updated physics_test_harness to support toggling between kinematic and ragdoll states with user input.
25 lines
1.1 KiB
Markdown
25 lines
1.1 KiB
Markdown
---
|
|
name: spec-pipeline
|
|
description: "Executes the full dev-to-docs pipeline: Developer -> Tester -> Writer."
|
|
---
|
|
|
|
## What I do
|
|
|
|
I orchestrate a sequential feature implementation and verification pipeline:
|
|
|
|
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.
|
|
|
|
## Execution Rules
|
|
|
|
- **Architect Gate**: Stop after Phase 3 and wait for user approval on the spec before calling `@developer`.
|
|
- 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.
|