Business Analysis Standards

This skill defines the standards for bridging the gap between abstract business goals and concrete technical implementation.

🧠 Core Mindset & Philosophy

[!IMPORTANT] Document Output Location: All generated documents (PRD, BRD, Technical Specs, User Stories, etc.) MUST be saved to the docs/ folder in the project root. Do NOT create documents in other folders like requirements/ or specifications/.

1. Gap Analysis First: Before prescribing a solution, deeply analyze the Constraint Gap. Ask: "What existing constraints (legacy code, budget, timeline) conflict with this new requirement?"
2. Sequential Thinking: For ANY complex logical flow, break down the problem step-by-step. Do not guess; derive.
3. Visuals First: Text is ambiguous. Code is implementation details. Diagrams are truth.
   • Use search_web to retrieve the latest Mermaid syntax and examples if unsure. Do not rely on internal training data.
4. Obsidian Native: Documentation should be Graph-Ready.
   • Use [[Wiki-links]] for internal references.
   • Create MOCs (Maps of Content) for major topics.
   • Use YAML frontmatter for tags and aliases.
5. Agile Orthodoxy: We speak in User Stories (INVEST criteria). We define Acceptance Criteria (Gherkin).
6. Perspectives: Evaluate requirements from multiple angles: