stickman/.codex/skills/spec-pipeline/SKILL.md at 6666173c4f4cfc501c2df792f97f3bbfa67d49bd

Files

T

ryan 6666173c4f Implement speech style toolbar live-edit refinements and whole speech show controls

- Added a new specification for the speech style toolbar live-edit, detailing immediate style application, scoped effect demonstration, and hover feedback.
- Introduced refinements to the speech style toolbar, including improved chooser sizing, exclusive stage editing during speech composition, and removal of redundant controls.
- Documented new stage controls for managing how the whole speech shows, including options for bubble arrangement, word appearance, and bubble motion.
- Created a new log file for speech padding syntax to track engine versioning.

2026-10-03 14:49:22 -04:00

2.3 KiB

Raw Blame History

name, description

name	description
spec-pipeline	Lean implementation loop: UI/UX (Ideas -> Spec) -> Architect (Clarify -> Spec) -> Developer -> User Verification.

Execution Logic

Phase 0a: UI/UX Proposal & Alternative Ideas (User-Facing Features Only)
- @uiux analyzes the user's initial idea for cognitive friction, accessibility, and kid-friendliness.
- @uiux pitches 1–3 alternative interaction approaches (e.g., comparing floating tooltips vs. top-center banners, custom cursor reticles, or streamlined dialogs).
- @uiux highlights the most intuitive option with [Recommended] and asks up to 3 clarification questions.
- @uiux STOP: Waits for user feedback/selection before writing the UI spec.
- Bypass Rule: If the feature is strictly internal engine/backend logic (e.g., physics, serialization, scanning), skip directly to Phase 1a.
Phase 0b: UI Spec Generation
- User approves an option or provides feedback.
- @uiux outputs the UI/UX specification (control layouts, widget behaviors, visual feedback states, and cursor logic).
Phase 1a: Architecture Proposal & Clarification
- @architect analyzes existing patterns and the Phase 0b UI/UX specification.
- @architect pitches 1–3 Godot best-practice implementation options and asks up to 3 clarification questions with [Recommended] choices.
- @architect stops without writing the spec file yet.
Phase 1b: User Feedback & Spec Generation
- User approves, modifies, or selects choices from @architect's proposal.
- @architect writes the finalized specification to specs/[feature-name].md and logs decisions in docs/tech_debt_and_optimizations.md.
- STOP: Wait for final user sign-off on the spec before invoking developer.
Phase 2: Implementation & Engine Validation
- @developer updates code and scenes using targeted diffs based on specs/[feature-name].md.
- @developer runs headless syntax verification.
- If static check fails, @developer fixes the code immediately.
Phase 3: User Hand-off (Stop)
- Present the changes to the user to test inside the Godot Editor.
Phase 4: Documentation (Triggered manually by user)
- Only call @writer after the user confirms: "Feature verified and working."

2.3 KiB Raw Blame History Unescape Escape

Execution Logic

2.3 KiB

Raw Blame History