By Richyboy170
Turn Claude Code + Obsidian into a second brain. The LLM incrementally ingests sources into a persistent, interlinked markdown wiki — building entity/concept/source pages, flagging contradictions, maintaining an index and log. Knowledge compounds instead of being re-derived by RAG on every query. Inspired by Karpathy's LLM Wiki gist. Ships SKILL, 3 sub-agents, 5 slash commands, 8 Python tools (stdlib only), full vault templates, and cross-tool compatibility (Claude Code, Codex CLI, Cursor, Antigravity, OpenCode, Gemini CLI).
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Ingest a source file from raw/ into the LLM Wiki — read, discuss, write summary page, update cross-references across 5-15 pages, regenerate index, append to log. Usage /wiki-ingest <path-to-source>
Bootstrap a fresh LLM Wiki vault with the three-layer structure, schema files, and starter templates. Usage /wiki-init <path> --topic "<topic>" [--tool all|claude-code|codex|cursor|antigravity]
Run a health check on the LLM Wiki vault — mechanical checks (orphans, broken links, stale pages, missing frontmatter, log gap, duplicates) plus semantic checks (contradictions, cross-reference gaps, concepts missing their own page). Outputs a markdown report with suggested actions. Usage /wiki-lint [--stale-days N] [--log-gap-days N]
Show recent entries from the LLM Wiki log (wiki/log.md). Uses the standardized
Query the LLM Wiki — reads index.md first, drills into 3-10 relevant pages, synthesizes an answer with inline [[wikilink]] citations, and offers to file the answer back as a new comparison or synthesis page. Usage /wiki-query "<question>"
Dispatched sub-agent that ingests a new source into an LLM Wiki vault. Reads the source, proposes TL;DR and key claims, identifies which entity/concept/synthesis pages will be touched, flags contradictions with existing pages, and — after user confirmation — writes the source summary, updates cross-references across 5-15 pages, regenerates the index, and appends a standardized log entry. Spawn when the user says "ingest this", "add this paper/article/book to the wiki", or drops a file into raw/.
Dispatched sub-agent that answers queries against an LLM Wiki vault. Reads index.md first, drills into 3-10 relevant pages across categories, synthesizes an answer with inline [[wikilink]] citations, and offers to file the answer back into the wiki as a new comparison or synthesis page. Spawn when the user asks a substantive question the wiki might answer, says "what does the wiki say about X", "compare A and B across my sources", or wants to explore a topic.
Dispatched sub-agent that runs a periodic health check on an LLM Wiki vault. Runs mechanical checks via scripts (orphans, broken links, stale pages, missing frontmatter, duplicate titles, log gaps), does semantic checks (contradictions, stale claims, cross-reference gaps, concepts missing their own page), and produces a markdown report with suggested actions. Spawn weekly, after batch ingests, or when the user says "check the wiki" / "lint my wiki" / "audit the vault".
Uses power tools
Uses Bash, Write, or Edit tools
Spec-driven, artifact-first software delivery for deep agents.
BMAD-Method Agentic SDLC is a layered software development lifecycle for agentic delivery. It uses Claude Code agents, specialist personas, BMAD skills, commands, and optional deterministic workflows to take software work from idea discovery through PRD, architecture, evaluation, story implementation, QA review, and delivery.
This repository is not primarily a website or app. Generated apps, app/, and sandbox/ are working surfaces and experiments. The core product is the agentic SDLC system.
| Layer | Role | Examples |
|---|---|---|
| Agent teams | Own lifecycle phases and specialist perspectives | cs-engineering-lead, cs-planning-lead, code-reviewer |
| Skills | Execute repeatable methods and quality gates | bmad-prd, bmad-dev-story, bmad-testarch-nfr |
| Commands | Provide user-facing entry points | /cs:workflow-build |
| Artifacts | Carry context across phase boundaries | prd.md, .decision-log.md, sprint-status.yaml |
| Workflow automation | Makes repeatable multi-agent runs deterministic | .claude/workflows/*.js |
flowchart TD
U[User goal, raw idea, or artifact paths] --> L[cs-engineering-lead]
L --> R[Phase 1: Research and discovery]
R --> P[Phase 2: PRD and requirements planning]
P --> A[Phase 3: Architecture, stories, readiness]
A --> E[Phase 4: Story implementation]
E --> Q[Phase 5: Independent QA review]
Q --> D[Final delivery digest]
R -. owns .-> RL[cs-brainstorm-research-lead]
P -. owns .-> PL[cs-planning-lead]
A -. owns .-> PL
E -. routed by .-> L
Q -. dispatched by .-> L
D --> NX[Next handoff or release decision]
The lifecycle is intentionally gated. Agents do not just chat toward code; they create artifacts, hand them off, verify them, and keep implementation tied to specs and acceptance criteria.
| Phase | Coordinator | Specialists | Primary Skills | Output Artifacts |
|---|---|---|---|---|
| 1. Research and discovery | cs-brainstorm-research-lead | cs-market-researcher, cs-tech-researcher, cs-problem-solver, cs-innovation-strategist, cs-visual-researcher, cs-concept-synthesizer, plus cs-design-thinker / cs-ideation-strategist when interactive facilitation is needed | bmad-brainstorming, bmad-market-research, bmad-domain-research, bmad-technical-research, bmad-prfaq, bmad-product-brief | Locked problem and ICP, alternatives, evidence, wedge, risks, assumptions, validation test, visual manifest when applicable |
| 2. PRD and requirements planning | cs-planning-lead | cs-concept-to-prd-planner, cs-requirements-architect, cs-prd-work-planner, cs-evaluation-architect, cs-prd-quality-reviewer, cs-epic-story-planner | bmad-prd, bmad-ux, bmad-testarch-test-design, bmad-testarch-nfr, bmad-review-edge-case-hunter | prd.md, addendum.md, .decision-log.md, FR/NFR/UJ IDs, evaluation spine, open questions |
| 3. Architecture, stories, readiness | cs-planning-lead | Planning specialists plus architecture and story workflows | bmad-create-architecture, bmad-agent-architect, bmad-create-epics-and-stories, bmad-create-story, bmad-story-automator-review, bmad-check-implementation-readiness, bmad-sprint-planning, bmad-sprint-status | Architecture artifacts, ADR/design decisions, epics, ready-for-dev stories, sprint-status.yaml, readiness verdict |
| 4. Story implementation | cs-engineering-lead | cs-frontend-engineer, cs-backend-engineer, cs-fullstack-engineer, cs-senior-engineer, cs-karpathy-reviewer | bmad-dev-story, bmad-code-review, bmad-quick-dev, bmad-testarch-atdd, bmad-testarch-trace, bmad-testarch-test-review, bmad-checkpoint-preview | Changed files, tests/checks run, implementation notes, file list, story status moved to review |
| 5. Independent QA review | cs-engineering-lead | code-reviewer, security-auditor, test-engineer, web-performance-auditor | code-review-and-quality, security-and-hardening, test-driven-development, performance-optimization, browser-testing-with-devtools | Findings by severity, coverage gaps, security risks, performance risks, approve/request-changes verdict |
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimnpx claudepluginhub richyboy170/agentic-sdlc-internship --plugin llm-wikiAutonomous experiment loop that optimizes any file by a measurable metric. 5 slash commands, 8 evaluators, configurable loop intervals (10min to monthly).
Workflow-builder skill: design and write deterministic multi-agent workflow scripts (.js files in .claude/workflows/) for Claude Code's Workflow tool (CLAUDE_CODE_WORKFLOWS=1, /workflows). Every session opens with an intake question set; when the user is vague, a stdlib recommendation engine infers and proposes a topology with rationale instead of stalling. Ships 3 stdlib Python tools (intake recommendation engine, .js validator enforcing the pure-literal-meta / no-non-determinism / guarded-loop / parallel-thunk rules, topology scaffolder), 3 references citing 7-8 authoritative sources each (full API surface, orchestration patterns, decision + intake guide), templates + a runnable example, cs-workflow-architect persona agent + /cs:workflow-build slash command. Use when building, scaffolding, or running a custom Claude Code workflow or orchestrating sub-agents (fan-out, pipeline, loop, judge-panel).
End-to-end Kubernetes Operator discipline: CRD design, reconcile-loop patterns, and OperatorHub Capability Levels. Ships CRD validator, reconcile-loop linter, and capability auditor (3 stdlib Python tools), 4 references on the operator pattern + CRD design + reconcile patterns + framework comparison (controller-runtime/kubebuilder/operator-sdk/metacontroller/KOPF), CRD + Go controller skeletons, and /operator-audit slash command. NOT a generic k8s skill — specifically the Operator pattern.
Hypothesis testing, A/B experiment analysis, sample size calculation, and confidence intervals. 3 stdlib-only Python tools with Z-test, t-test, chi-square, effect sizes, power analysis, and Wilson score intervals.
End-to-end chaos engineering discipline: design experiments with hypothesis + steady-state metric + blast radius + abort criteria, calculate risk score against error budget, and generate blameless postmortems. 3 stdlib Python tools (experiment_designer, blast_radius_calculator, experiment_postmortem), 4 references on chaos principles + experiment design + 7-attack taxonomy + tooling landscape (Chaos Toolkit/Mesh/Litmus/Gremlin/AWS FIS/DIY), templates for plans + postmortems, and a /chaos-experiment slash command. Composes with feature-flags-architect (kill switches as abort triggers) and kubernetes-operator (chaos targets).
Comprehensive C4 architecture documentation workflow with bottom-up code analysis, component synthesis, container mapping, and context diagram generation
Harness-native ECC plugin for engineering teams - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
Superpowers Plus core skills library for Claude Code: planning, execution routing, TDD, debugging, and collaboration workflows
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.