wicked-understanding

Generate a wiki skill (agent-loadable) from repo-intelligence analysis artifacts into the per-repo store at $ARTIFACTS_DIR/skills/{repo-slug}-wiki/ and install it via npx skills add. Also generates viewer.html on demand from ~/.wicked-understanding/ data. Trigger on: "generate wiki", "build wiki", "document this repo", "create the wiki skill", "build docs", "show me the wiki", "open the viewer". Requires analysis artifacts from repo-analyst.

Orchestrate all repo-intelligence lens skills with diff-awareness and parallel execution. Use when someone wants to analyze a repo (fully or partially), refresh outdated analysis, or run the full pipeline before forging a skill or building a wiki. Automatically detects which lenses are stale using manifest files and only re-runs what has changed. Runs all needed lenses in parallel when subagents are available. The lens subagents always produce the analysis by reading the repo at HEAD — that is the accurate, current source of truth. wicked-brain is an OPT-IN, additive build-time enricher (via `--enrich-from-brain`, default off): after the lens artifacts exist, it can append supplementary design rationale (ADRs, recorded decisions) the lenses cannot see; it never replaces a lens or overrides a lens fact. Trigger on: "analyze this repo", "refresh the analysis", "update the knowledge base for X", "run the pipeline on Y", "analyze and generate wiki", or whenever repo-skill-forge or repo-wiki-planner is about to ru

Generate or refresh the always-in-context agent context doc (CLAUDE.md / AGENTS.md / GEMINI.md) for an analyzed repo, distilled from the lens artifacts and routing agents to the generated task skills + wiki. This is the cheapest always-loaded surface: it orients every session in a few dozen lines and points at the curated skills instead of re-exploring the codebase. Merge-safe — augments a managed block, never clobbers hand-written rules. Trigger on "generate the context doc", "write the CLAUDE.md", "create AGENTS.md from the analysis", "orient agents to this repo", or after the skills + wiki are generated.

Generate task-oriented workflow skills for a codebase into the per-repo store and install them via npx skills add. Produces fix-bug, add-feature, verify, write-tests, add-domain, and scaffold skills — each tailored to this repo's specific patterns, file paths, and conventions. The verify skill describes what each capability should observably do and how to prove it, so anyone can test the repo without reading the code. Skills progressively load deeper context from the wiki refs as the agent needs it. Trigger on: "build the skills", "generate the workflow skills", "make the dev skills", "forge the skills", or after repo-analyst completes analysis.

Analyze the architecture of a code repository — component structure, layering, data flow, dependency direction, and cross-cutting concerns. Run independently whenever someone wants to understand how a codebase is structured, needs an architecture diagram, or wants to review architectural patterns. Requires a survey (run repo-surveyor first if `survey.md` doesn't exist). Writes `architecture.md` and a manifest sidecar so repo-analyst can detect when this lens needs refresh.

Analyze the functional domain and business logic of a code repository — entities, operations, invariants, workflows, and external integrations. Run independently when someone needs to understand what a system does (not how it's built), review domain logic, or map business rules. Requires a survey; run repo-surveyor first if needed. Writes `domain.md` and a manifest sidecar. Trigger on phrases like "what does this system do", "explain the business logic", "what are the domain entities", "how does the billing/auth/ordering work".

Analyze the operational setup of a code repository — how to install, run, build, test, debug, and deploy it. Run independently when someone needs to set up the project, understand the CI/CD pipeline, work with environment configuration, or debug operational issues. Requires a survey; run repo-surveyor first if needed. Writes `ops.md` and a manifest sidecar. Trigger on phrases like "how do I run this", "how do I set it up", "what are the environment variables", "how does deployment work", "how do I run tests".

Perform a fast, structured survey of any code repository to understand its technology stack, file structure, entry points, dependencies, and key files. Use whenever someone asks to understand, explore, or get oriented in a codebase — even casually. Always the mandatory first step before any lens skill or repo-analyst. Triggers on any repo path, GitHub URL, or uploaded archive regardless of language or framework. Run this even if you think you already know the stack — the survey feeds all downstream skills.

Analyze the technical implementation patterns, coding conventions, APIs, key algorithms, and idioms of a code repository. Run independently when someone needs to understand how code is written (not what it does), review coding patterns, understand the API surface, or onboard to technical conventions. Requires a survey; run repo-surveyor first if needed. Writes `technical.md` and a manifest sidecar. Trigger on phrases like "what are the coding conventions", "how is error handling done", "what patterns are used", "explain the API", "how do I add a new feature".

Living wiki for acme-payments.