phase-prep
Research Godot source code to prepare critical implementation notes for upcoming phases. Use before implementing phases to avoid debugging sessions and discover Godot quirks upfront.
Profile →npx skills add majiayu000/claude-skill-registry --skill phase-prep --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Phase Prep: Godot Source Research for Implementation Planning ## Overview This skill helps prepare for implementing a new phase by researching Godot's DAP implementation using the `godot-source` MCP server. The goal is to extract non-obvious insights, discover quirks, and create strategic implementation notes that will help the implementing agent avoid debugging sessions. **Key Principle**: Extract insights and point to details, don't duplicate code. The implementing agent will also have access to `godot-source`. **Examples of valuable findings from previous phases:** - ✅ **stepOut command not implemented** (would have caused hang without this knowledge) - ✅ **ConfigurationDone required** (breakpoints timeout without it) - ✅ **Two-step launch process** (launch + configurationDone to trigger) - ✅ **Event filtering critical** (DAP sends async events mixed with responses) --- # Process ## 🎯 Phase 1: Understand the Phase Plan ### 1.1 Read the Phase Details First, understand what the phase is supposed to implement: ```bash # Read the phase from PLAN.md Read docs/PLAN.md # Focus on the target phase section: # - Tools to implement # - Success criteria # - Critical implementation notes
- Overview
- 🎯 Phase 1: Understand the Phase Plan
- 1.1 Read the Phase Details
- 1.2 Extract Investigation Targets
- 1.3 Review Previous Phase Patterns
- 🔍 Phase 2: Research Godot Source
- 2.1 Check Godot Memories First
- 2.2 Verify Command Support
- 2.3 Extract Critical Insights
- 2.4 Compare with Our Patterns
- 📝 Phase 3: Create Implementation Notes
- 3.1 Create the Notes Document
- 3.2 Fill in the Template
- 3.3 Cross-Reference with Existing Docs
Read the phase from PLAN.md Read docs/PLAN.md Focus on the target phase section: Review our established patterns Read .serena/memories/critical_implementation_patterns.md Common patterns to verify against Godot: Use godot-source MCP server to list available memories Read relevant memories for the phase, especially focus on those that being with "dap_". For example: Search for command implementation.
What does the phase-prep skill do?
Research Godot source code to prepare critical implementation notes for upcoming phases. Use before implementing phases to avoid debugging sessions and discover Godot quirks upfront.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill phase-prep --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.