Codename-Inc

👻 | Transform requirements into executable tasks - primary agent

👻 | Independent multi-lens review of plan.md and/or tasks.md — finds overengineering, missing verification, hallucinated deps, weak references

👻 | Unified planning entry point - researches, assesses complexity, routes to workflow - primary agent

👻 | Transform requirements into executable tasks - primary agent

👻 | Independent multi-lens review of plan.md and/or tasks.md — finds overengineering, missing verification, hallucinated deps, weak references

👻 | Unified planning entry point - researches, assesses complexity, routes to workflow - primary agent

Run the SPECTRE release workflow, including version bumps, Codex sync, global Codex install verification, GitHub release, manual npm publish handoff, npm verification, and final global Codex refresh.

Use when starting implementation, debugging, or feature work on a project with captured knowledge.

Use when modifying build loop code, debugging stats/token tracking, adding CLI features, changing iteration prompts, or understanding how spectre-build works end-to-end

Use when modifying the plan loop, debugging plan stages, changing clarification flow, scope isolation, or understanding how spectre-build --plan works end-to-end

Use when modifying the ship loop, debugging ship stages, changing clean/test/rebase behavior, or understanding how spectre-build --ship works end-to-end

Use when user wants to search for existing knowledge, recall a specific learning, or discover what knowledge is available.

Use when planning product scaling, adding GUI/server layers, multi-model support, adversarial reviews, live steering, telemetry, scheduling/triggers, or node-based pipeline editors to spectre-build

Use when working with pipeline stages, completion strategies, build loop orchestration, or the web GUI for spectre-build

Use this skill when you see @name or /name patterns in user input without file identifiers. This means the user is trying to call a subagent or slash command using Spectre Agent Tools. The @ prefix dispatches to a subagent (e.g., '@tdd-agent write tests', '@code-reviewer check this file'). The / prefix executes a slash command (e.g., '/spectre:scope', '/spectre:plan'). Both require Spectre CLI to run specialized agents and predefined prompts.

Use when starting implementation, debugging, or feature work on a project with captured knowledge.