Skip to content

Detailed Business Analysis, Requirements Engineering & Architect Modes for better context #1129

@pssah4

Description

@pssah4

Problem:

User is not able to specify his problem, needs and idea for a solution. User is also not able to give details for a technical planning.

Solution:

I have created a Business Anayst and a Requirements Engineer Chatmode. These two can be used very early stage to scope and work thru the exploration and ideation phase of any project. The Business Analyst uses a interview-style chat with the user, the requirements engineer scopes the ideated solution into features.

It could be used before the /speckit.specify to create deep basic understanding of the problem, users, and needs as staring point for the project, its scope, goals and desired maturity (simple test, PoC, MVP). The generated business-analys.md and Features can be used as context for the /specify prompt.

The Architect chatmode the again chats with the user to define a target architecture, which coud be use as reference for the /speckit.plan prompt. Again, the created ADRs, Arc42 can be used as context for the /plan prompt.

Business Idea → Requirements → Context for /specify
        ↓           ↓             
   BA Agent    RE Agent    
Architecture → Contex for /plan
      ↓            
Architect Agent  

Maybe helpful :-)

Chatmodes and instructions: https://github.com/pssah4/digital-innovation-agents.git

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions