specode

Plugin specode from marketplace pluginhub in qxbyte/pluginhub. Commands read from the repo's manifest — 1 month ago.

Skills (7)

• continue

  Use when resuming an existing spec by slug — the /specode:continue entry that reads the fixed docs, reports a progress brief (inferred phase + checkbox progress), then stops and waits for the user; it never auto-resumes. Trigger /specode:continue <slug>.

• distill

  Use when distilling a finished specode spec into atomic, locate-oriented markdown knowledge points — writes cases/ + navigation/ + MEMORY.md into the project's own <project_root>/knowledge-base/ (md-only, no auto-injection), optionally copied to an Obsidian vault. Trigger ONLY /specode:distill <slug

• execute

  Use when running a spec's execution tail — presents the 执行方式 selector, dispatches the chosen engine (task-swarm / superpowers / specode-native TDD), then runs acceptance and the distill prompt. Trigger /specode:execute <slug> manually at any time once tasks.md exists, or invoked by name (specode:exe

• intake

  Use when running specode's requirements phase — project analysis + code location + clarification, then writing requirements.md. Produces <specsRoot>/<slug>/requirements.md (with the project_root frontmatter contract) plus the location pointers handed to the design phase. Invoked by name (specode:int

• list

  Use when listing all specs under the specs root — the /specode:list entry that shows every spec slug with its inferred phase, for looking up slugs or an overview; it does not resume. Trigger /specode:list.

• spec

  Use when creating a new spec-driven workflow — the /specode:spec entry that walks requirements → design → tasks → 执行方式 → execute → acceptance, autonomously calling superpowers skills for the heavy lifting with a first-class specode-native fallback, and filing 4 fixed artifacts (requirements.md / des

• using-specode

  Overview of the specode plugin and how to activate it — the spec-driven workflow, its five commands, and when to enter spec mode. On Kimi Code this is loaded at session start via the manifest's sessionStart.skill; on hosts with a SessionStart hook the same advisory is injected by the hook instead.

Hooks (1)

• SessionStart

  sh "${CLAUDE_PLUGIN_ROOT}/scripts/run.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/spec_hooks.py" session-start

Similar plugins