メニュー
End-to-end Spectra development orchestration: plan → design → implement → build → test → scoped QA. Use for full features, large refactors, or when the user wants the full dev cycle with sub-skill routing.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Serena MCP Tools — Semantic code analysis and editing with clangd for C++20 and Python
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
Drives a live Spectra instance via the embedded MCP automation server (default http://127.0.0.1:8765/mcp). Use for smoke tests, screenshots, UI commands, figure/series setup, and visual debugging after builds — whenever validating rendering without writing a harness.
Spectra Agent Skill Set
Plan, design, and implement Spectra C++/GLSL/Python changes. Use when breaking down a feature, making architecture decisions before coding, or writing/fixing source in src/, include/spectra/, shaders, tests, or python/.
Spectra git and release workflows: conventional commits, branches, PRs, version bumps, release tags, merge conflicts, changelog. Use for commit, branch, PR, release, version.txt, squash merge, cherry-pick, or git status/diff questions.
| name | spectra-dev |
| description | End-to-end Spectra development orchestration: plan → design → implement → build → test → scoped QA. Use for full features, large refactors, or when the user wants the full dev cycle with sub-skill routing. |
Coordinate skills — do not skip planning; do not run QA before build+tests are green.
spectra-implementation (plan → design? → code)
→ build-and-test (compile + ctest)
→ loop on FAIL until green
→ scoped QA (qa-orchestrator or single qa-* skill)
→ report to user
| Stage | Skill |
|---|---|
| Plan / design / code | spectra-implementation |
| Build / test | build-and-test |
| Visual change | graphical-change-workflow |
| Full QA | qa-orchestrator |
| Paths | QA skills |
|---|---|
src/ui/theme/ | qa-designer-agent, qa-accessibility-agent, qa-regression-agent |
src/gpu/shaders/ | qa-regression-agent, qa-performance-agent |
src/render/vulkan/ | qa-regression-agent, qa-memory-agent, qa-performance-agent |
src/core/ | qa-performance-agent, qa-regression-agent, qa-api-agent |
src/ipc/, src/daemon/, src/agent/ | qa-api-agent, qa-performance-agent |
python/ | qa-api-agent |
include/spectra/ | qa-api-agent, qa-regression-agent |
src/anim/ | qa-performance-agent, qa-regression-agent |
| ROS adapters | qa-ros-performance-agent |
| Unknown / release gate | qa-orchestrator |
| Failure | Action |
|---|---|
| Build fail | fix via spectra-implementation → rebuild |
| Test fail | fix → re-run build-and-test |
| QA finding | fix → re-run affected qa-* only |
| 3+ cycles | pause; ask user |
## Development Complete: <title>
### Done
### Files changed
### Evidence (build, tests, QA)
### Follow-ups
Domain work: use spectra-index.