business-knowledge-workflow_skill

Overview

This skill defines a practical workflow for capturing business knowledge from external docs (like iWiki), validating it against code, and producing high-quality Skill documentation. It guides the full cycle: document retrieval, code cross-check, and distilled Skill output suitable for developers and maintainers. The goal is reproducible, verifiable architecture documentation that stays aligned with the codebase.

How this skill works

First, search and extract relevant pages from iWiki or other doc systems to build a preliminary knowledge framework (concepts, architecture, flows, data models). Next, locate and inspect core code artifacts (classes, methods, config) to verify and supplement the documentation. Finally, refactor and condense the findings into a layered Skill document with an overview, architecture, core flows, config reference, and a code index.

When to use it

• Onboarding to a new module or subsystem
• Verifying iWiki or legacy docs against the implementation
• Creating or updating module architecture documentation
• Converting dispersed knowledge into a reusable Skill
• Preparing reference material for debugging or feature work

Best practices

• Start with targeted searches (module name + keywords) to limit noise
• Treat code as the source of truth and annotate mismatches in the doc
• Apply a layered structure: overview → details → code examples
• Prefer tables and code indexes over long prose for quick lookup
• Keep docs concise: remove duplicates and merge related content

Example use cases

• Extract Buildless module concepts from iWiki, verify with code, and produce a 500-line refactored architecture doc
• Cross-check Redis key formats and method call chains described in docs against actual Kotlin classes and mark differences
• Create a compact Skill overview for a microservice with a code index and configuration table for on-call engineers
• Split a large reference page into a core Skill for daily use and a reference folder for deep-dive material