analysis-advisor

Recommends requirements analysis and modeling techniques based on system characteristics and team experience.

23|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/jdm4pku/RE-Skills --skill analysis-advisor-jdm4pku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analysis-advisor
Source: https://github.com/jdm4pku/RE-Skills/tree/main/skills/analysis-advisor
Command: npx skills add https://github.com/jdm4pku/RE-Skills --skill analysis-advisor-jdm4pku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often default to a single analysis technique (typically use cases) regardless of system type, or skip visual modeling entirely, which consistently misses 15-30% of requirements. This Skill guides you through a structured selection process to pick the right combination of analysis techniques for your specific project. ## Core Features & Use Cases - Adaptive Questionnaire: Four questions about requirement type focus, system complexity, team modeling experience, and key concerns drive the recommendation. - Technique Recommendation Matrix: Maps answers to specific techniques including use cases, user stories, process models, data models, state models, decision tables, dialog maps, and context diagrams. - Use Case: A team building a chemical inventory system with complex lifecycle states answers the four questions and receives a tailored recommendation: context diagram, data dictionary, user stories, a state model for chemical records, and a decision table for disposal authorization rules. ## Quick Start Ask the analysis advisor which modeling techniques to use for your project by describing your system type, complexity, team experience, and biggest requirements concern.

Frequently Asked Questions about analysis-advisor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose which requirements analysis techniques to use?▼

Answer four questions about your requirement type focus, system complexity, team modeling experience, and biggest concern. The advisor maps your answers to a recommended set of techniques such as use cases, state models, decision tables, or data models.

What is the difference between use cases and user stories for requirements?▼

Use cases detail actor-system interactions with alternate and exception flows, suiting transaction-heavy systems and experienced teams. User stories capture user needs with acceptance criteria and work better for agile teams with basic modeling experience.

When should I use state models instead of use cases?▼

Use state models when the system has complex object lifecycles, event-driven behavior, or regulatory constraints on state transitions. Use cases are weak at revealing unhandled states, while state transition tables force explicit handling of every state-event combination.

Which analysis techniques should every project always apply?▼

Every project should create a context diagram to define the system boundary and external interfaces, plus a data dictionary to define system vocabulary and prevent ambiguity. All other techniques are selected based on system characteristics.

What are the risks of using too many modeling techniques?▼

Over-modeling extends the analysis phase unnecessarily and produces models nobody reviews. A simple system needs only 2-3 techniques, and even complex systems rarely need more than 5 well-chosen ones.