felipefontoura/acme-store-sdd — explained in plain English
Analysis updated 2026-05-18
Set up a visible GitHub Projects board that tracks a team's spec-driven development process.
Automatically move a feature's board card forward each time a review stage gets approved.
Enforce approval and passing checks before merging using branch protection rules.
See where a team's real bottleneck is by watching where cards pile up on the board.
| felipefontoura/acme-store-sdd | 100/dotfiles | adams549659584/my-openwrt-actions | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | Shell | Shell | Shell |
| Last pushed | — | 2016-11-18 | 2020-06-06 |
| Maintenance | — | Dormant | Dormant |
| Setup difficulty | moderate | easy | hard |
| Complexity | 3/5 | 1/5 | 3/5 |
| Audience | developer | developer | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires creating a GitHub repo, running a setup script, and adding a fine-grained access token as a secret.
Acme Store is a small reference project that shows how a team can practice something called Spec-Driven Development, or SDD, using tools that most teams on GitHub already have access to. It is a companion example for a separate project called the Pi SDD Kit, and its whole purpose is to demonstrate one specific idea: that this careful way of planning and building software can be done openly, as a team, with everyone able to see where each piece of work stands. The core method behind SDD is a sequence of stages that a feature moves through, starting with an idea and a plan, then a written requirements document, a detailed specification, a task breakdown, the actual coding work, and finally a review, before being marked done. Each step in that sequence requires a human to approve it before the work can move to the next stage. This repository's contribution is connecting that sequence to a visible GitHub Projects board, so the current stage of every feature is something the whole team can see at a glance, rather than something tracked only in someone's head or a private document. Behind the scenes, each feature keeps a small file that records its current stage and whether it has been approved. A GitHub Actions workflow watches for changes to that file, and automatically moves the corresponding card on the project board to the next column the moment an approval happens. Rules on the main branch also require an approval and passing checks before anything can be merged, so the approval step becomes something enforced by the system, not just a suggestion. Setting this up involves creating a new GitHub repository, running an included script that creates the project board's columns and configures branch protection, and adding an access token so the automation is allowed to move cards. The author frames the board as more than documentation: watching where work piles up on it, especially during the coding stage, reveals where a team's real bottleneck actually is.
A reference project showing how a team can practice Spec-Driven Development using a visible GitHub Projects board that automatically moves cards as work gets approved.
Mainly Shell. The stack also includes Shell, GitHub Actions, GitHub Projects.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.