Example project

BA Toolkit ships with a complete example project so you can see exactly what the pipeline produces before running it on your own idea.

Lumen Goods

Lumen Goods is a fictional sustainable home-goods D2C (direct-to-consumer) online store. The example was generated by running the full BA Toolkit pipeline from /discovery through /implement-plan, plus the /risk and /sprint utility skills. Every artifact is realistic, cross-referenced, and ready for development.

Domain: E-commerce Slug: lumen-goods Artifacts: 16 files

Artifact inventory

#	Artifact	What it contains	File
0	Discovery	Problem space, audience hypotheses, MVP feature ideas, domain recommendation	00_discovery_lumen-goods.md
0a	Principles	Language, ID conventions, Definition of Ready, NFR baseline, quality gates	00_principles_lumen-goods.md
1	Brief	Goals, audience, stakeholders, risks, constraints	01_brief_lumen-goods.md
2	SRS	Functional requirements, roles, business rules (IEEE 830 structure)	02_srs_lumen-goods.md
3	User Stories	Stories grouped by Epics, with priority and requirement references	03_stories_lumen-goods.md
4	Use Cases	Main, alternative, and exception flows for each user goal	04_usecases_lumen-goods.md
5	Acceptance Criteria	Given/When/Then scenarios linked to each user story	05_ac_lumen-goods.md
6	NFRs	Performance, security, availability targets with measurable metrics	06_nfr_lumen-goods.md
7	Data Dictionary	Entities, fields, types, constraints, relationships	07_datadict_lumen-goods.md
7a	Research	Technology decisions (ADRs), integration map, storage choices	07a_research_lumen-goods.md
8	API Contract	Endpoints, request/response schemas, error codes	08_apicontract_lumen-goods.md
9	Wireframes	Screen layouts, components, navigation flows (text descriptions)	09_wireframes_lumen-goods.md
10	Scenarios	End-to-end user journeys linking stories, criteria, wireframes, and API calls	10_scenarios_lumen-goods.md
11	Handoff	Development package — artifact inventory, MVP scope, open items	11_handoff_lumen-goods.md
—	Risk Register	Risks scored by probability x impact, with mitigation strategies	00_risks_lumen-goods.md
—	Sprint Plan	Stories grouped into sprints by velocity and capacity	00_sprint_lumen-goods.md

What to look for

• Cross-references. Open the SRS and notice how each functional requirement (FR-001, FR-002, …) links forward to user stories. Open the stories and see how each story links back to its source FR and forward to acceptance criteria.
• Traceability. The handoff document includes a coverage summary showing what percentage of requirements are covered by stories, acceptance criteria, and other downstream artifacts.
• Domain-specific content. Because the domain is E-commerce, the artifacts include industry-specific concepts like product catalogs, cart management, checkout flows, payment processing, and order fulfillment.
• Consistent terminology. The same terms and IDs are used across all 16 artifacts — no drift between “shopping cart” in one file and “basket” in another.

How to use this example

1. Browse the artifacts above to understand what each pipeline step produces.
2. When you run BA Toolkit on your own project, compare your output to the Lumen Goods example to gauge completeness.
3. The example is read-only and ships with the npm package — it is not affected by your own pipeline runs.