Status transitions are validated rather than free text, and requirements, tasks and decisions link both ways, so what implements a requirement and why something is blocked become queries rather than archaeology. The interview tools are the on-ramp — they turn a vague ask into a structured requirement without anyone filling in fields by hand.
A software lifecycle server backed by a database file per project. It holds requirements, implementation tasks and architecture decision records, links them to each other, validates the status transitions between states, and reports on the whole thing.
- Requirements created, searched, read in full with their relationships, and moved through their lifecycle with each transition validated
- A requirement traced through to the tasks and architecture decisions that implement it
- Tasks created against requirements with effort, assignee, parent task and acceptance criteria, then searched and updated
- Tasks synced from their linked issues, one at a time or all at once, with conflicts detected
- Architecture decisions recorded with context, drivers, options considered and consequences, then searched, updated and reviewed
- A project dashboard with requirement and task statistics, completion percentages and blocked items
- Guided interviews that gather a requirement or an architectural brief question by question and create the record at the end
- The project exported as structured Markdown, and Mermaid diagrams generated for requirements, tasks, architecture or dependencies
Python, and a database file per project — its path is supplied as an environment setting and the schema is created on first run. No account, no key. Issue sync only applies to tasks you have already linked.
One command — pip install -e .