business-knowledge-workflow

Business Knowledge Workflow

Applicable Scenarios

Need to quickly understand an unfamiliar business module
Need to obtain background knowledge from iWiki or other documentation systems
Need to cross-validate documentation descriptions against actual code
Need to distill knowledge into a skill, architecture document, or module description

Already clearly know which piece of code to modify and just need to implement it
Just compressing an existing skill, no need to reacquire business knowledge
Just adding ordinary explanations, no need to form reusable knowledge assets

This skill focuses on "understand first, then verify, finally distill", not directly modifying code.
Business knowledge acquisition is usually divided into three stages:
- Document discovery and initial screening:reference/1-document-discovery.md
- Code cross-validation:reference/2-code-cross-check.md
- Distill into skill / architecture document:reference/3-skill-distillation.md
Document content is by default not trustworthy enough to be directly restated; it must be verified through code or runtime paths.
When distilling, prioritize writing module boundaries, key objects, main paths, and common pitfalls, rather than copying encyclopedia-style explanations.
If the final output is a skill, also check skill-writer。

Business documents and code implementations are often not fully consistent
A good business knowledge document should be able to answer "what problem does this module solve, what is the main path, and where to look first when making changes"
Distillation results should prioritize serving subsequent development and troubleshooting, rather than preserving a pile of raw materials

Only reading documents without doing code verification
Copying external materials verbatim into a skill
Output structure lacks a sense of boundaries, causing it to keep expanding later