kb_skill

Overview

This skill encodes a complete, opinionated knowledge base management rule set for project workspaces. It enforces creation, synchronization, auditing, and context-acquisition behaviors so the knowledge base remains a single source of truth. Use it to detect missing documentation, automate updates after code changes, and guide migration of legacy solution packages.

How this skill works

On invocation it inspects the helloagents/ directory for core files (CHANGELOG.md, project.md, wiki/*) and evaluates quality across completeness, format, consistency, and security. If the knowledge base is missing or severely out of sync, it triggers a codebase scan to reconstruct required files. For each change, it parses plan/YYYYMMDDHHMM_<feature>/ files to extract requirements, ADRs, and tasks, then updates wiki and history destinations, cleans obsolete entries, and records migration summaries.

When to use it

• When initializing a new workspace or running an ~init command to create a SSOT
• After code changes that must be reflected in documentation (APIs, data models, architecture)
• When the knowledge base is missing, incomplete, or contains severe inconsistencies
• During release planning to migrate legacy solution packages from plan/ to history/
• As a routine audit to detect sensitive information or format/consistency issues

Best practices

• Always store knowledge base files under helloagents/ to preserve SSOT conventions
• Trigger synchronization immediately after code changes to avoid drift
• Mark owning modules in requirements extracted from plan/*/why.md to keep specs aligned
• Batch large module creations (≤20 modules per batch) to avoid overloading scans
• Treat SSOT as outdated if it conflicts with executed code; update docs from execution facts

Example use cases

• Run during development to parse a completed plan/ solution package and update wiki/modules/<module>.md
• Detect missing wiki/ files and create minimal CHANGELOG.md, project.md, wiki/overview.md, arch.md, api.md, data.md
• After an API refactor, update wiki/api.md and wiki/data.md, add ADRs to wiki/arch.md, and link to history/
• List legacy plan/ packages and prompt the user to migrate selected items into history/YYYY-MM/
• Perform a quality pre-check and flag severe issues that require a full rebuild