Research & Analysis Workflows

Close out a finished work cycle by distilling what was learned into a durable, per-module knowledge base — a file-based memory indexed by source file — so future PRDs, tasks, and agents reuse recorded decisions, gotchas, patterns, and contracts instead of re-deriving them. Use this skill at the END of a cycle, after implement-task and/or review, when the user says "close the cycle", "capture what we learned", "update the knowledge base", "record the learnings", "remember this for next time", or "post-mortem this feature". This is different from for-research (upfront, per-big-task, disposable): close-cycle writes permanent memory keyed to code units and grows across cycles.

Research a BIG task upfront and cache the findings as a structured Markdown knowledge base (a file-based RAG) so that any later prompt, agent, or workflow step can retrieve exactly the context it needs in one shot — without re-exploring the codebase or overflowing the context window. Use this skill whenever a task is too big to hold in one prompt, whenever the user says "research this first", "cache the context", "build a knowledge base", "prepare context for the agents", or before starting a large feature, migration, or refactor. Also use it when repeated conversations keep re-discovering the same codebase facts.

Break a PRD (Product Requirements Document) down into small, self-contained tasks organized as a file-based kanban board, designed so multiple AI agents can execute tasks in parallel. Each task is its own Markdown file. Use this skill whenever the user asks to turn a PRD, spec, or requirements document into tasks, tickets, a backlog, a kanban board, or a parallelizable work breakdown — even if they don't say "kanban". Also use it right after generating a PRD when the user asks "now split this into tasks" or "plan the implementation".

Fast path for a small, self-contained change that doesn't justify the full PRD → kanban → implement pipeline — a cosmetic tweak, a copy/text change, a tiny localized bugfix, moving or restyling one element. Use this skill when the user asks for a single obvious change that touches one or two files with no design decision, no new module/API/schema, and no need for parallel agents — e.g. "move this button", "change the header color", "fix this label's text", "bump the timeout", "tweak the spacing". Escalate to write-prd / prd-to-kanban the moment it turns out bigger than that.