--- name: knowledge-architecture-2bc16187ba5a description: Build a static-first knowledge architecture using file-backed domain maps, rules, hypotheses, and durable references. Use for knowledge architecture, learning systems, decision context, and long-lived team memory without runtime memory tooling. metadata: category: user-invoked version: 1.0.0 tags: knowledge-management, documentation, learning-system, decision-making disable-model-invocation: true --- Default output: return only the result, blockers, and required evidence. Omit preambles, process narration, repeated context, confidence scores, and follow-up offers. Use at most five bullets unless a required artifact or schema needs more. # Knowledge Architecture Skill ## Purpose Create a durable, file-backed knowledge system that helps the team keep shared context, decisions, rules, and open questions in one place. This milestone is **static-first**: - no hooks - no MCP - no custom tools - no runtime memory engine Use markdown files, links, and clear ownership. ## When to Use - Starting a knowledge base for a product or domain - Reorganizing scattered planning notes into canonical files - Turning repeated context into stable rules and references - Establishing decision, quality, and review links around a domain ## Canonical Inputs - `templates/knowledge/index.md` - `templates/knowledge/domain.md` - `templates/knowledge/knowledge.md` - `templates/knowledge/hypotheses.md` - `templates/knowledge/rules.md` - `docs/knowledge/README.md` Related records: - `templates/decisions/decision.md` - `templates/quality/gate.md` - `templates/review/maintenance-review.md` ## Target Structure Prefer this shape: ```text docs/knowledge/ ├── README.md ├── index.md ├── domains/ │ └── .md ├── entries/ │ └── .md ├── hypotheses.md └── rules.md ``` ## Workflow 1. **Define scope** - What product, system, or domain does this cover? - What should be durable vs still uncertain? 2. **Create the index** - Start from `templates/knowledge/index.md`. - Capture domains, key knowledge, rules, open hypotheses, and linked records. 3. **Map domains** - Create one file per meaningful domain from `templates/knowledge/domain.md`. - Keep boundaries explicit. 4. **Capture atomic knowledge** - Use `templates/knowledge/knowledge.md` for durable facts, patterns, or references. - Favor small entries with strong links. 5. **Track uncertainty** - Use `templates/knowledge/hypotheses.md` for claims that need validation. - Every hypothesis should have an owner or next validation step. 6. **Write rules** - Use `templates/knowledge/rules.md` for stable operating rules. - Link each rule to evidence, decisions, or prior incidents when possible. 7. **Link adjacent systems** - Stable choices belong in `docs/decisions/`. - Repeatable checks belong in `docs/quality/`. - Recurring health checks belong in `docs/reviews/maintenance/`. ## Writing Rules - Keep titles crisp. - Prefer one idea per file. - Mark uncertainty instead of hiding it. - Link laterally across knowledge, decisions, quality, and reviews. - Avoid session-specific chatter. ## Done Criteria - `docs/knowledge/index.md` exists or is updated. - Core domains are listed. - Durable knowledge is separated from hypotheses. - Rules are explicit. - Related decisions, gates, and reviews are linked. ## Anti-Patterns - Giant undifferentiated notes - Rules without rationale - Decisions embedded in random meeting notes - Hypotheses presented as settled facts - Runtime tooling assumptions in milestone 1 ## Anti-Rationalization Table | Excuse | Counter | |--------|---------| | "We can organize the knowledge base later" | Disorganized knowledge is lost knowledge. Structure it while the context is fresh. | | "One big document is easier to maintain" | Giant undifferentiated notes are impossible to navigate. Split by domain. | | "Hypotheses should be marked as facts for clarity" | Marking uncertainty as fact corrupts the knowledge base. Be honest about what is known. | | "Rules don't need rationale" | Rules without rationale are ignored. Explain the why behind each rule. | | "We don't need a knowledge base for this project" | Every project accumulates knowledge. Without a home for it, it lives in people's heads. | --- Source attribution: v1truv1us Original project: https://github.com/v1truv1us/ai-eng-system/blob/eaff192b6e8bcb204a1f1b132b98f748a9b4572e/plugins/ai-eng-learning/skills/knowledge-architecture/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2025 John Ferguson Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: v1truv1us Original project: https://github.com/v1truv1us/ai-eng-system/blob/eaff192b6e8bcb204a1f1b132b98f748a9b4572e/plugins/ai-eng-learning/skills/knowledge-architecture/SKILL.md Attribution basis: Source repository record Fields of work: Marketing, Operations, Product Management, Project & Program Management Roles: Business Process Analyst, Content Marketer, Marketing Analyst, Product Manager, Project Manager Specialties: Notion Tools: Tool not specified Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 978537e2562634293a34b56f76e1ddfdefeb27aae6be263f43cb6744000debf5