ai-skills

Use when a repo, project, or area has accumulated several design/spec/plan docs and needs ONE coherent, top-down design document that synthesizes them and routes a reader to the right spec for depth. Create or update after a release or major implementation cycle, when onboarding needs a current architectural view, or when it is unclear which spec is current versus superseded. Trigger phrases: "update the design doc", "sync the design doc", "design-doc", "compile the design", "give me a top-down view of the design".

Phase 2 of design thinking. Synthesize understanding into a precise problem definition and spec. Produces a spec with explicit success/failure criteria. Input: context brief from /understand. Invoke after Understand, or when Ideate reveals the spec is too vague.

Entry point for the 5-phase design thinking process. Assesses current state and routes to the appropriate phase skill. Each phase runs in an isolated agent session and produces a concrete artifact. Phases: understand → define → ideate → prototype → test. Invoke when starting any non-trivial problem or creative task.

Phase 3 of design thinking. Generate and select an approach, then produce a concrete implementation plan. Input: spec from /define. Invoke after Define, or when Prototype reveals a fundamental design issue requiring replanning.

Phase 4 of design thinking. Execute the plan to produce a working artifact. Input: plan from /ideate and spec from /define. For code: uses superpowers execution skills. For writing/creative: produces the draft artifact. Invoke after Ideate.

Phase 5 of design thinking. Audit the implementation against the spec. Produces an audit document. Input: implementation from /prototype + spec from /define. Invoke after Prototype. NOT the same as /design-doc — this evaluates a specific implementation cycle, not the system's full architecture.

Phase 1 of design thinking. Map the problem space thoroughly before defining or solving. Produces a context brief. Invoke at the start of any non-trivial problem, or when a later phase reveals the problem was not well understood.

Use when the user wants to compile a set of pulled sources into a structured, cross-linked wiki. Natural triggers: "/ingest", "compile these papers into a wiki", "synthesize my sources", "ingest the X papers focusing on Y", "build me a wiki page per method from these papers". Distinct from /pull (fetches sources) and /sota (produces a state-of-the-art review). Input: a folder of Markdown sources (typically `./sources/`). Output: cross-linked pages in `./wiki/` with per-source summaries and synthesis pages.

Use when user asks for a deep, source-grounded audit of an academic document — diploma, master's thesis, doctoral thesis, or paper. Natural triggers: "/review", "audit this paper", "deep review of the thesis we just opened", "vamos a revisar la tesis de X", "audita este documento". Distinct from /revise (blog prose) and /code-review (PR diffs). Produces a narrative report (5–18 pages by level) plus a structured forensic assembly sibling, plus per-phase artifact files, all in the document's own language. Multi-phase pipeline with three parallel extractors, nine parallel evaluators, a synthesizer, and a final narrative redactor — total 14 subagents, single level of indirection.

Use when the user wants a structured state-of-the-art review of a topic, built from a corpus of already-pulled sources and/or wiki pages. Natural triggers: "/sota", "haz un estado del arte sobre X", "build a SOTA on X from my sources", "do a SOTA review on X", "tengo N papers sobre X, organízame el estado del arte". Distinct from /review (audits an existing document) and /ingest (compiles sources into wiki). The output is a single Markdown report organised BY DIMENSIONS (paradigms, techniques, domains, evaluation methods, etc.) — never chronological. Plan-first: the agent proposes dimensions from the corpus and the user approves before fan-out. Multi-phase pipeline with one dimension per synthesizer subagent (4–7 in parallel) plus a final assembler.

Use when the user wants to extract a Zettelkasten-style atomic note from a source. Natural triggers: "/distill", "make this a Zettel", "pull the claim out of …", "what's the atomic note here?", "atomic-ize this", "extract a Zettel from this". Source can be: the current conversation, one or more files the user names explicitly, a pulled source, a transcription, or multiple drafts converging on a shared idea. Output: one or more draft Markdown files in `./notes/atomic/`, ready for the user to review and promote into their canonical notes.

Use when the user wants to pull, fetch, download, crawl, or save a webpage, paper, news article, blog post, PDF, DOCX, or any other external document into the local `./sources/` folder as Markdown with provenance frontmatter. Natural triggers: "/pull", "pull this", "download this article", "save this paper", "get the X homepage", "fetch this PDF". Distinct from `WebFetch` which is for one-shot reads — `pull` archives a citable copy.