Debrief
Long-running open-source maritime analysis workbench (active since the 1990s) using Spec Kit to drive a documentation and migration effort.
Reviewed 2 months ago · Jul 18, 2026
- Stars
- 27
- Contributors
- 31
- Open issues
- 629
- Age
- 12 years
- Last push
- 2 months ago
- Latest release
- 20250307_3_1_44 Mar 7, 2025
View weekly commit data
| Week starting | Commits |
|---|---|
| Aug 30, 2026 | 0 |
| Aug 23, 2026 | 0 |
| Aug 16, 2026 | 0 |
| Aug 9, 2026 | 0 |
| Aug 2, 2026 | 0 |
| Jul 26, 2026 | 0 |
| Jul 19, 2026 | 0 |
| Jul 12, 2026 | 0 |
| Jul 5, 2026 | 0 |
| Jun 28, 2026 | 0 |
| Jun 21, 2026 | 6 |
| Jun 14, 2026 | 0 |
| Jun 7, 2026 | 0 |
| May 31, 2026 | 0 |
| May 24, 2026 | 0 |
| May 17, 2026 | 0 |
| May 10, 2026 | 0 |
| May 3, 2026 | 0 |
| Apr 26, 2026 | 0 |
| Apr 19, 2026 | 0 |
| Apr 12, 2026 | 0 |
| Apr 5, 2026 | 4 |
| Mar 29, 2026 | 0 |
| Mar 22, 2026 | 0 |
| Mar 15, 2026 | 0 |
| Mar 8, 2026 | 2 |
| Mar 1, 2026 | 7 |
| Feb 22, 2026 | 8 |
| Feb 15, 2026 | 0 |
| Feb 8, 2026 | 0 |
| Feb 1, 2026 | 4 |
| Jan 25, 2026 | 0 |
| Jan 18, 2026 | 0 |
| Jan 11, 2026 | 2 |
| Jan 4, 2026 | 42 |
| Dec 28, 2025 | 0 |
| Dec 21, 2025 | 0 |
| Dec 14, 2025 | 0 |
| Dec 7, 2025 | 0 |
| Nov 30, 2025 | 2 |
| Nov 23, 2025 | 0 |
| Nov 16, 2025 | 0 |
| Nov 9, 2025 | 0 |
| Nov 2, 2025 | 0 |
| Oct 26, 2025 | 0 |
| Oct 19, 2025 | 0 |
| Oct 12, 2025 | 0 |
| Oct 5, 2025 | 0 |
| Sep 28, 2025 | 0 |
| Sep 21, 2025 | 0 |
| Sep 14, 2025 | 0 |
| Sep 7, 2025 | 0 |
Metrics updated Aug 30, 2026 · collected automatically from the GitHub API
Spec structure
- Location
.specify/ and specs/- Formats
- Markdown
- Notes
.specify/holds Spec Kit'smemory/,scripts/, andtemplates/; a rootspecs/directory contains numbered feature folders such as001-document-debrief-algorithms. Default branch isdevelop.
Assessment drift: moderate
Spec-to-code drift
Moderate. The specs/ directory has been untouched since 2026-02-07 while code kept moving through at least
2026-06-21 — roughly four and a half months of divergence. The nuance: Spec Kit appears to have been adopted for a
bounded initiative (documenting algorithms ahead of a migration) rather than for ongoing feature development, so
the stale specs describe a completed effort more than an abandoned practice. We rate it moderate rather than high
because the specs still accurately scope the initiative they were written for.
Defects and rework
Not yet assessed.
Maintenance outcomes
A useful pattern to watch: SDD applied as a campaign tool for a specific initiative inside a 30-year-old codebase, rather than as the project’s day-to-day workflow. Whether the spec directory gets revived for the next initiative or quietly rots will say a lot about how bounded adoption plays out.
Timeline
-
Code development continues
Latest commit on the develop branch, with specs untouched since February.
-
Last spec change
Specification added for documenting Debrief algorithms and tools for migration.
-
Spec Kit adopted
First commit to the .specify/ directory.