Results for “knowledge”

Relentlessly interview the user about THEIR plan or design — one question at a time — resolving each branch of a decision tree until shared understanding. Claude is the interviewer; the user is the interviewee. Triggers on "grill me", "stress-test this plan", "get grilled on my design", "interrogate my plan". Checkpoints every answer to docs/knowledge/<slug>.md so progress survives a context-window reset. Flags knowledge the user cannot answer as a gap to chase. Do NOT use to PROPOSE solutions or compare approaches (→ mk:brainstorming). Do NOT use to validate "is this worth building?" (→ mk:office-hours). Do NOT use when Claude should ANSWER questions about the repo (→ mk:ask-me). Do NOT use for a one-shot review of an existing plan (→ mk:plan-ceo-review). Do NOT use to apply named reasoning lenses to findings (→ mk:elicit).

The English summary is being prepared. Showing the original description.

A persistent, compounding knowledge base combining Karpathy's LLM Wiki pattern with a structured knowledge graph. Ingest documents once — the LLM writes wiki pages, extracts entities/relations into the graph, and stores raw content for evidence retrieval. Knowledge accumulates and cross-references; it is never re-derived from scratch. Use when building a knowledge base from many documents that should accumulate and cross-reference over time instead of being re-read each session.

The English summary is being prepared. Showing the original description.

Drafts one knowledge article or known-error article from a resolved incident or ticket thread: symptoms as reported, environment, cause exactly as the resolver stated it, resolution steps as performed, workaround with its limits, verification, things tried without effect, related records, keywords and proposed metadata, every statement traced to a ticket note or marked UNKNOWN, with a redaction log and a question list for the knowledge owner. Never decides a root cause, adds a step or publishes. Use when the user asks to "write a KB article from this ticket", "turn this resolved incident into a knowledge article", "draft a known error record for this", "document the fix we just did" or "make this thread into a how-to for the service desk". Do not use for a procedure the team will execute (runbook, operating procedure, playbook), use runbook-drafter instead; for a post-incident review, use incident-postmortem-drafter. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

Knowledge base synthesized from the Guide to the Systems Engineering Body of Knowledge (SEBoK) v2.14 by the BKCASE Project. Use for the established systems-engineering canon: SE fundamentals and foundations (systems science, systems thinking, the systems approach, modelling/MBSE), the life cycle (ISO/IEC/IEEE 15288/24748/24774 process, development & agile approaches, model selection/tailoring), technical management, concept definition, architecture/realization (the Vee), V&V, maintenance/sustainment, SE standards, and the application contexts (product, service, enterprise, systems-of-systems, healthcare), plus enabling SE (business/team/individual), related disciplines, quality attributes/specialty engineering, implementation examples, and emerging knowledge. Good for grounding background, vocabulary, and prior-art positions across all eight SEBoK Parts. SCOPE LIMITS: this pack is SEBoK v2.14 only (released 2026-05-18); it synthesizes and signposts rather than reproducing the source — it does not reproduce ISO/IEC/IEEE standard text, is a curated guide (not a complete textbook), and is thin on AI-integration depth (Part 8 is a staging area, not settled practice). LICENCE: content is CC BY-NC-SA 3.0 — non-commercial use only, attribution to the BKCASE Project required, share-alike obligations carry forward.

The English summary is being prepared. Showing the original description.

Knowledge graph and smart memory management using graphify + Obsidian-inspired patterns. Use when: setting up a knowledge graph, managing memory health, cross-linking notes, compiling wiki pages from scattered notes, adding structured frontmatter, or running memory health checks. Triggers on: 'knowledge graph', 'graphify', 'wiki', 'cross-link', 'memory health', 'frontmatter', 'compile notes', 'wikilinks'.

The English summary is being prepared. Showing the original description.

knowledge/raw/ の生の学びを分類・統合して knowledge/curated/ に書き出す。 ディスパッチャーが閾値超過で起動したキュレーターから呼ばれるほか、 「知見を整理して」と言われたときに使う。

The English summary is being prepared. Showing the original description.

Structured interview and observation techniques for extracting tacit knowledge from domain experts

The English summary is being prepared. Showing the original description.

Auto-generate knowledge YAML from the codebase. Use when the user runs /sync-knowledge or wants knowledge files refreshed.

The English summary is being prepared. Showing the original description.

Manages project knowledge using ByteRover context tree. Provides two operations: query (retrieve knowledge) and curate (store knowledge). Invoke when user requests information lookup, pattern discovery, or knowledge persistence. Developed by ByteRover Inc. (https://byterover.dev/)

The English summary is being prepared. Showing the original description.

Review and search project knowledge that gstack has collected across work sessions. Find past lessons, prune outdated entries, and export recorded knowledge when you need to revisit earlier solutions or organize what the project has learned.

• Reviewing lessons from previous work sessions
• Searching for a solution used before
• Pruning outdated project knowledge

Store facts, daily events, and user preferences in files that persist across sessions. Organize knowledge with PARA, a method separating projects, ongoing responsibilities, references, and archives, and retrieve saved information through qmd search.

• Keeping facts available across sessions
• Recording daily events and conversations
• Organizing knowledge about people and projects

Turn an incident review into an HTML presentation covering the root cause, fix, and follow-up actions. Use a dedicated template with speaker notes to help engineering, reliability teams, and leadership discuss next steps.

• Presenting an incident review
• Explaining a bug's root cause and fix
• Discussing systemic follow-up actions

Turn content into a Xiaohongshu-style series of knowledge cards, with a cover, one key point per card, and a closing summary. Large text, soft colors, and a screenshot-friendly layout support preparing image posts.

• Turning practical tips into a series of knowledge cards
• Preparing a carousel post for Xiaohongshu
• Creating image posts for WeChat Moments

Ask questions about a codebase using a knowledge graph, a map of its components and relationships. Get explanations tied to specific files, functions, dependencies, and architectural layers, with warnings when the graph may be outdated.

• Understanding how a feature works
• Finding callers and dependencies
• Locating code related to a concept

Extract classes, functions, modules, and their relationships from source code or documentation into AgentDB. Build a knowledge graph, a map of connected entities, to understand code structure, dependencies, and potential change impacts.

• Understanding a codebase's structure
• Investigating dependencies between modules
• Assessing the impact of code changes

Explore a knowledge graph, a network of entities and relationships, from a chosen starting point. Rank relevant paths and summarize dependencies or indirect connections to help understand code structure and assess the impact of changes.

• Assessing the impact of changing a component
• Tracing dependency chains
• Discovering indirect connections between entities

Store and retrieve knowledge across agent sessions with AgentDB. Organize memories into tiers, search learned patterns, combine related memories into context, and record causal links to support later work.

• Reuse knowledge from previous agent sessions
• Store and search learned patterns
• Combine related memories into context

Create or improve Claude skills that package specialized knowledge, repeatable workflows, and tool instructions. The guide covers planning SKILL.md and supporting files, generating a starter folder, validating the structure, and packaging the result as a distributable ZIP.

• Turning recurring tasks into a reusable skill
• Packaging company knowledge and procedures for Claude
• Improving an existing skill after practical use

Create a specialized Claude Code subagent with Hindsight long-term memory. Start with an empty agent or import prepared documents, then equip it with knowledge pages and memory search to reuse information across sessions.

• Create a specialized agent that remembers across sessions
• Build an agent from prepared reference documents
• Start an empty agent and add knowledge over time

Store team conventions, troubleshooting notes, and project knowledge on a self-hosted Hindsight server. Retrieve relevant context before new tasks and draw on recorded experiences, including successful procedures, failed attempts, and individual preferences attributed to specific people.

• Share project conventions across the team
• Record fixes and troubleshooting procedures
• Recall past decisions before starting work

Plan a central board for internal announcements, with fields for authors, audiences, publication dates, expiry dates, and acknowledgements. On request, generate empty templates in CSV, SQL, JSON Schema, or a Notion property mapping.

• Organizing company news that gets lost in chat
• Preparing an announcement board template
• Defining publication, acknowledgement, and expiry steps

Build and maintain a Markdown knowledge store with source links for individual claims. Use Git checks to detect changes in the code a page describes, and archive outdated pages while preserving their history.

• Compile notes and papers into source-linked wiki pages
• Verify numbers and quotations against original sources
• Check whether code documentation needs updating

Create or update Claude skills that capture specialized knowledge and repeatable workflows. Guides the organization of instructions, scripts, references, and templates, then covers initialization, validation, and packaging into a distributable skill file.

• Turning recurring work into a reusable Claude skill
• Organizing internal knowledge and API instructions
• Revising an existing skill after practical use

Build a lasting Markdown knowledge base for project decisions, architecture, and session discoveries. Search pages by keywords and tags, use results to answer with citations, and check for outdated content, broken links, and structural problems.

• Preserving project decisions across sessions
• Finding past debugging discoveries
• Checking knowledge pages for broken links and stale content