S
SmartAndPoint/ProjectStore
Decisions, specs and stories as plain markdown, for every coding agent.
★ 13·updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
After install: how to tell it works
- What you see after install — The command exits 0 and the terminal shows no "command not found" or "permission denied".
- One-line self-check — Run the smallest usage example from that repository's README. If the output matches what the README describes, it is working.
- If that does not work — This project has no troubleshooting notes. Search its issues for "install".
The install command comes from the repository; these checks describe observable results only and do not replace the project's own docs.
- Star count
- 13 ★ · SmartAndPoint/ProjectStore · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-20 · last seen 2026-11-20 · seen 1× · listed by 1 sources
- Score
- score 103 · 13 ★ · 1 sources · repo
- Install
- see Install & config above
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Open Source. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
SmartAndPoint/ProjectStore;first catalogued 2026-11-20;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# ProjectStore
Excerpted from the repository README (abridged)
> ProjectStore is a method and a framework for building apps and services of any size with AI agents. It keeps the project's record — what was decided, what is in flight, what was checked — as reviewed markdown in git, readable by any agent and anyone with the repo.
A project workflow plugin for Claude Code and OpenAI Codex (experimental). Both are released together at one version, and one command sets a project up for either or both: see Install.
## Two months of agents, and nobody knows why
Agents write code fast. They re-decide settled questions even faster: every fresh session arrives empty, makes its own architectural call, and commits under its own assumptions. Two months later you have noodle code — every strand reviews fine on its own, and each was written under a different theory of the project. Ask "why is this a queue and not a cron job?" and nobody can answer. The agent that decided is long gone.
The fix is not a smarter agent. It is a loop with verification in it.
## Where it fits
Not agent memory. Not a spec pipeline. The project's record. Three kinds of tools sit next to a coding agent. Each answers a different question.
| Kind of tool | The question it answers | What it keeps | Examples |
| Agent memory | What does this agent recall? | Notes the model keeps from its sessions, for an agent, a user or a machine. | Mem0, Zep, Codex and Claude Code memory |
| Instruction files | How should an agent behave here? | Standing rules for an agent, kept in the repository. | CLAUDE.md, AGENTS.md, rules, steering files |
| Spec-driven tools | How do we build this change? | A spec, a plan and tasks for one feature. | Spec Kit, Kiro, OpenSpec, BMAD |
| ProjectStore | What has the project decided, what is in flight, and was it checked? | Decisions, specs and work items with a status, a date and links, in git. A person approves each before ProjectStore writes it; a fresh-context critic reviews it by rule. | — |
Keep your agent's memory for you and your machine, and the project in the vault.
Decision logs, validators, session-start orientation and independent review each exist elsewhere. What ProjectStore adds is all of them over one linked record. Tool by tool, with sources: docs/alongside.md.
## The loop
The thing that makes agentic coding work — the loop Claude Code's own creator keeps pointing at — is gather context, act, verify, repeat. ProjectStore runs that loop one level up: over the project, not just the code.
1. You hand the agent a task. It opens an artifact before it opens an editor: an ADR if something needs deciding, an epic and stories for the work, a spec when the "how" is non-trivial.
2. A fresh-context critic attacks the artifact. Expect revise — on this repo it has yet to pass anything on the first try, and that is the point.
3. The fixed artifact lands in the backlog; the kanban regenerates itself.
4. An agent picks up a story. A planner reads how earlier epics actually landed in the code and says where this change belongs.
5. By rule, a reviewer matches the diff against the story's acceptance criteria — per criterion, with evidence — before anything gets called done.
A project workflow plugin for Claude Code and OpenAI Codex (experimental). Both are released together at one version, and one command sets a project up for either or both: see Install.
## Two months of agents, and nobody knows why
Agents write code fast. They re-decide settled questions even faster: every fresh session arrives empty, makes its own architectural call, and commits under its own assumptions. Two months later you have noodle code — every strand reviews fine on its own, and each was written under a different theory of the project. Ask "why is this a queue and not a cron job?" and nobody can answer. The agent that decided is long gone.
The fix is not a smarter agent. It is a loop with verification in it.
## Where it fits
Not agent memory. Not a spec pipeline. The project's record. Three kinds of tools sit next to a coding agent. Each answers a different question.
| Kind of tool | The question it answers | What it keeps | Examples |
| Agent memory | What does this agent recall? | Notes the model keeps from its sessions, for an agent, a user or a machine. | Mem0, Zep, Codex and Claude Code memory |
| Instruction files | How should an agent behave here? | Standing rules for an agent, kept in the repository. | CLAUDE.md, AGENTS.md, rules, steering files |
| Spec-driven tools | How do we build this change? | A spec, a plan and tasks for one feature. | Spec Kit, Kiro, OpenSpec, BMAD |
| ProjectStore | What has the project decided, what is in flight, and was it checked? | Decisions, specs and work items with a status, a date and links, in git. A person approves each before ProjectStore writes it; a fresh-context critic reviews it by rule. | — |
Keep your agent's memory for you and your machine, and the project in the vault.
Decision logs, validators, session-start orientation and independent review each exist elsewhere. What ProjectStore adds is all of them over one linked record. Tool by tool, with sources: docs/alongside.md.
## The loop
The thing that makes agentic coding work — the loop Claude Code's own creator keeps pointing at — is gather context, act, verify, repeat. ProjectStore runs that loop one level up: over the project, not just the code.
1. You hand the agent a task. It opens an artifact before it opens an editor: an ADR if something needs deciding, an epic and stories for the work, a spec when the "how" is non-trivial.
2. A fresh-context critic attacks the artifact. Expect revise — on this repo it has yet to pass anything on the first try, and that is the point.
3. The fixed artifact lands in the backlog; the kanban regenerates itself.
4. An agent picks up a story. A planner reads how earlier epics actually landed in the code and says where this change belongs.
5. By rule, a reviewer matches the diff against the story's acceptance criteria — per criterion, with evidence — before anything gets called done.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/smartandpoint-projectstore/)
- Source
- github · https://github.com/SmartAndPoint/ProjectStore
- Browse by field
- Open source
- Traction
- 13 ★
- added
- today
More entries
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.