Interviews, notes, internal policies, current processes, constraints and a document template.
SUB–05 / REQUIREMENTS · EVERYDAY ASSISTANT · HUMAN CONTROL
Business Requirements Analyst
A system that automates requirements work, from source materials to draft documents structured against GOST and ISO templates. Nine assistants cover stages from interview analysis to artifact generation. Each requirement is linked to a source, while unsourced items are flagged for review. Local deployment is supported; installation requirements are confirmed before launch.
A draft specification: boundaries, roles, requirements, scenarios, acceptance criteria and open questions.
- Local mode: in a configuration with no external integrations, data and computations remain within the approved environment
- Reduced effort: extraction, structuring, and draft preparation against GOST and ISO templates are automated
- More transparency: every requirement is linked to its source, traceability is end-to-end
- Nine assistants cover all stages — from collecting requirements to finished documents
01Capabilities
What the subagent can do.
Each function operates within defined boundaries and returns a result that can be verified before the next action.
Multi-agent analysis (9 agents)
Nine assistants run the stages of analytical work: interviews, document analysis, requirements, processes, completeness checks and preparation of the final documents.
Full document processing
PDF, DOCX and images are recognized locally in Russian and English. Every requirement is linked to a fragment of the source document.
Multi-standard compiler
GOST 19.201-78, GOST 34.602-89 and ISO 29148:2018. New standards are added through configuration, without rebuilding the system.
Project knowledge model
Requirements, sources and links are stored in a single knowledge model: the system finds contradictions, duplicates and missing conditions across the whole project.
Artifact generation
DOCX, PDF, Markdown, JSON, YAML with full Cyrillic support, traceability tables and links between goals, requirements and scenarios.
Audit and traceability
Every change is recorded in the audit log with the ability to replay the course of work. The project state is versioned.
A team or local perimeter with access only to the materials of the specific project.
Priorities, project boundaries and the final revision of the specification are approved by the product owner and the team.
02Process
Four steps within a familiar workflow.
Context remains traceable: each step shows its input, operation, result, and handoff to a human reviewer.
Collect
Combines the materials and records the source of each requirement.
Separate
Separates goals, functional and non-functional requirements, constraints and wishes.
Verify
Finds contradictions, duplicates, missing conditions and unverifiable wording.
Formalize
Prepares the specification, the acceptance criteria and the list of decisions the team must make.
Structured resultA draft specification: boundaries, roles, requirements, scenarios, acceptance criteria and open questions.
The result can be reviewed, adjusted, and passed to the next participant without copying a long conversation.
03Advantages
Both the value and its rationale are visible.
Each proposed outcome includes its verification method, limitations, and completion criteria.
Local deployment
In a local configuration with no external integrations, computations run on your hardware and data remains within the approved organizational environment.
Confidentiality
In a local configuration, information is processed within the organization. Work involving trade secrets or personal data requires configured access controls and review by the organization's specialists.
Source controls
Each requirement must reference a source. Automated checks flag unsourced requirements and broken links for correction.
Extensibility without rebuilding
The system structure is described to a single standard, so new features and modules are added predictably, without rebuilding the core.
Flexible standards
GOST and ISO templates are available. A qualified specialist reviews the finished document for compliance; new profiles can be added through configuration.
Reproducible deployment
Storage, document processing, and models are deployed through one procedure; environment requirements are checked before launch.
- Local mode: in a configuration with no external integrations, data and computations remain within the approved environment
- Reduced effort: extraction, structuring, and draft preparation against GOST and ISO templates are automated
- More transparency: every requirement is linked to its source, traceability is end-to-end
- Nine assistants cover all stages — from collecting requirements to finished documents
04Roles and perimeter
Who benefits and on what terms.
Each role gets a concrete result, while sources, integrations and control are fixed before integration.
| Role | What they get |
|---|---|
| Analysts and systems engineers | Automation of the routine extraction and structuring of requirements from documents and interviews. |
| Project managers | Control over the completeness and quality of requirements through gap detection and traceability. |
| Architects | A ready-made DDD decomposition with bounded contexts, aggregates and domain events. |
| Organizations with strict security requirements | A local deployment with no cloud integrations in the approved configuration. |
Boundaries and responsibility
The team assistant supports the process without becoming an autonomous decision-maker.
The subagent structures the materials, but does not define business priorities and does not confirm feasibility without the involvement of product, development and domain experts.
- Access rights and approved sources are defined before integration.
- Critical actions require human confirmation.
- Integrations and the deployment environment are selected after reviewing the process.
First step
Choose a ready-made solution or describe your process.
Pick one of the twelve agents and subagents, or fill in the questionnaire for custom development.