S
SmartAndPoint/ProjectStore
Decisions, specs and stories as plain markdown, for every coding agent.
★ 13·更新 2026-11-19
在 GitHub 查看 ↗直链 · 无中转页
装完之后怎么算装好了
- 装完该看到什么 — 命令正常结束时退出码为 0,终端里没有 "command not found" 或 "permission denied"。
- 一行自检 — 按该仓库 README 里给出的最小用法跑一次;能按 README 的描述输出就是通了。
- 答不出来怎么办 — 这个项目没有写排错说明,去仓库的 Issues 搜 install。
安装命令取自该仓库;以上判据只描述可观察到的结果,不替代项目自己的文档。
- ★ 数取值
- 13 ★ · SmartAndPoint/ProjectStore · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-11-20 · 最近见到 2026-11-20 · 共见到 1 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 13 ★ · 1 个来源 · repo
- 安装
- 安装命令见上方「安装与配置」。
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: 开源项目。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
SmartAndPoint/ProjectStore;我们收录于 2026-11-20;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# ProjectStore
以下摘录自该仓库的 README(片段)
> 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.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/smartandpoint-projectstore/)
- 来源
- github · https://github.com/SmartAndPoint/ProjectStore
- 按领域浏览
- 开源项目
- Traction
- 13 ★
- 收录于
- 今天
更多条目
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。