CodeWiki

Launch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, when a task complete, or combined bug/security and code-quality branch audits.

Executes CodeWiki phase plans one task at a time with focused implementation, plan updates, verification, and pending wiki follow-up. Use when the user asks to implement or continue tasks, process a task file, finish the next unchecked item, run verified development work, or handle pending absorb state during the build loop.

Searches the local CodeWiki and synthesizes grounded answers with citations to wiki pages. Use when the user asks how the project works, why a decision was made, where knowledge lives, what is known about an entity/issue/lesson/source, or whether a substantial answer should be filed back into the wiki.

Extracts durable CodeWiki knowledge from recent code changes, git diffs, changed files, and phase outcomes. Use when a phase is complete, pending absorb state exists, substantial coding work has landed, or lessons/entities/issues/decisions from implementation should be proposed for human-approved wiki updates.

Routes the current request to the right CodeWiki skill based on user intent and repository state. Use when the user asks what to do next, wants the recommended workflow, resumes a session, starts a feature, reacts to pending absorb state, or needs help choosing between CodeWiki skills.

Fluxo de trabalho com IA em 3 fases — Explorar (brainstorm guiado), Planejar (plano com tarefas atômicas) e Executar (passo a passo). Ative esta skill sempre que o usuário digitar `/explorar`, `/planejar` ou `/executar`, ou quando tiver qualquer objetivo que envolva planejamento, criação ou dúvida aberta. Serve tanto para tarefas de código quanto para tarefas do mundo real (escrever, pesquisar, contatar, montar). Idioma pt-BR.

Converts a CodeWiki PRD into implementation phases, actionable tasks, and relevant files. Use when codewiki-prd has produced a PRD, a PRD exists but no phase plan exists, the user asks to break down work, or codewiki-process needs an execution-ready plan.

Finds important but undocumented CodeWiki entities, concepts, decisions, lessons, or issues by scanning wikilinks, backlinks, repeated mentions, and code-backed references. Use when the wiki has thin pages, missing high-signal pages, repeated unresolved links, or the user asks to expand the knowledge graph.

Digests raw source documents into human-approved CodeWiki pages with summaries, entities, decisions, links, index updates, log entries, and source drift checks. Use when new material appears under wiki/raw, the user asks to process docs, ingest articles/papers/transcripts/specs, bulk-import sources, or update the wiki from immutable raw evidence.

Audits CodeWiki health for contradictions, broken wikilinks, orphan pages, stale code claims, source drift, frontmatter/tag problems, oversized pages, and log/index issues. Use when wiki drift is suspected, contested knowledge needs review, a periodic health check is due, or large batches of wiki changes need validation.

Configures and audits CodeWiki as an Obsidian-compatible markdown vault while preserving CodeWiki schema, raw-source immutability, wikilinks, attachments, Dataview-ready frontmatter, graph readability, and vault sync safety. Use when setting up Obsidian, managing assets, migrating an existing vault, or reviewing Obsidian navigation quality.

Drafts an implementation-ready Product Requirements Document from a feature idea using repository and wiki context. Use when the user wants to plan a new feature, clarify product intent, define scope before implementation, capture acceptance criteria, or start the CodeWiki PRD -> tasks -> process development workflow.