task-use-research-context-strategy

To analyze business rules and workflows, you must specify the domain question, scope, and depth level. The skill extracts domain-specific glossaries, if/then rules, and end-to-end process flows directly from your documentation and codebase with cited evidence.

Mapping business logic requires tracing domain rules across documentation and code. This process clarifies user needs, ensures system constraints are met, and identifies inconsistencies between requirements and existing implementations to reduce ambiguity.

Extracting a domain-specific glossary involves targeting your research scope to the new project. You define the desired depth level for analysis, allowing the tool to uncover and clarify core business terms, entities, and processes automatically.

Yes, tracing end-to-end process flows is a core function. By analyzing your provided documentation and code, it follows the execution of business logic across the system and maps the complete workflow with supporting sources.

Yes, specifying the scope and desired depth level is required before extracting business rules. Providing targeted domain questions ensures the analysis accurately extracts if/then logic and aligns with your specific research goals.

You should not use this strategy if you lack accessible documentation or codebase access. The analysis depends on reading existing text and code to extract glossaries, rules, and flows, making it ineffective for undocumented greenfield projects.