project-requirements

You can generate an IEEE 830-style SRS document by inputting your stakeholder interview notes, which the system translates into formal requirements, user stories with acceptance criteria, and traceability matrices. It uses structured templates to ensure complete specification coverage.

Yes, you can create bilingual BM/EN proposals and government RFx templates tailored for Malaysian contexts. The system formats client-facing documents and integrates pricing sections to align with local government procurement requirements.

You build a traceability matrix by processing stakeholder interviews through a structured pipeline that automatically attaches each generated requirement and user story to traceability links. This ensures every artifact maps directly back to its originating specification.

Yes, the SRS generator works with ASCII wireframes and integrates with the sales-planner skill to populate pricing sections. This combination allows you to produce technical specifications and client-facing proposals with accurate cost estimates.

The best way to write user stories with acceptance criteria is to feed your raw stakeholder interview transcripts into the system. It automatically extracts functional needs and formats them into structured stories complete with testable acceptance conditions.

You should avoid using this approach if your project lacks stakeholder interview data or operates outside Malaysian government RFx contexts, as the templates rely heavily on bilingual BM/EN inputs and structured IEEE 830 pipelines to generate valid outputs.