Built with SpecWeave
We use SpecWeave in our own product development: defining changes, recording task progress, checking the result, and handing unfinished work to the next coding session. These projects show the kinds of work the workflow supports.
Products in the workflow
| Project | Product context |
|---|---|
| EasyChamp | Sports leagues, club tools, and related web and mobile applications. EasyChamp predates SpecWeave; we use the workflow for ongoing changes to the platform. |
| JobWeave | Job search, tailored resumes, recruiter context, and interview preparation. |
| Verified Skills | A skill registry with source and security evidence, accompanied by vskill and Skill Studio for local skill development and evaluation. |
| SpecWeave | The CLI, dashboard, documentation, and workflow itself. We use the same specifications and task records while improving SpecWeave. |
More application examples
The project showcase also includes mobile apps, learning tools, and games:
- Football 2026 / WC26: a World Cup travel companion.
- Lulla: baby audio classification and soothing tools.
- SkillUp Football: football coaching and training.
- BizZone: business and student events.
- SketchMate: a drawing game with AI judging.
- EduFeed: AI-assisted learning.
These are project examples, not a benchmark of development speed or reliability. Using SpecWeave does not mean an entire product's history was created through the workflow.
What we carry between sessions
An intent records the desired outcome. When a change needs explicit scope, an increment adds acceptance criteria and tasks. Completion records link the work to its evidence, and a handoff identifies what remains.
This makes the next session easier to start: read the shared intent, inspect the specification and completed work, then continue from the next action. The same record remains useful when the coding agent, model, or person changes.
For public development history, inspect the SpecWeave repository and vskill repository. For the workflow, start with your first project, the dashboard, or cross-tool handoffs.