Materials
Manual, use cases, training, video and deep explanations — generated from your own code and your application actually running, not from a document someone promised to write. When the system changes, you regenerate it.
One command, two manuals: the technical one with architecture, diagrams and code excerpts; the user one with step-by-step instructions and screenshots captured from your application actually running. No stale screenshot pasted in by hand.
Walks the screens, integrations and flows you actually shipped and writes the use cases in Cockburn format — main flow, exceptions, diagrams and wireframes. It’s the documentation the product team asks for and nobody has time to write.
Every use case runs against the live application, as the right user, and is checked on screen as well as in the database. What comes out is a report with a verdict per flow and screenshot evidence of the bugs found — before your customer finds them.
A single document that explains a module, an entity, a screen or a concept of your system, joining the business view with the technical one. It’s there to decide, to review, and to answer the question only one person on the team used to be able to answer.
Builds training programs in tracks by audience — support, sales, engineering, whichever you define — with markdown chapters, diagrams, real screenshots and narrated video. Onboarding stops depending on the senior’s calendar.
A narrated, captioned video tutorial, produced by driving your real application to capture the journey. Ready for internal training, a sales demo, or support material.
Records the mind map of the work session so you can pick up exactly where you left off — after a meeting, a week away, or a handoff to someone else on the team.
Everything on this page runs today and is what keeps Spaccy's own documentation up to date. Request early access to try it before everyone else.
