drewsonne/maya-project
Code reviewこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
Maya dates project management — issues, decisions, product docs, and the project skills as a Claude Code plugin marketplace
概要
Project management hub for the Maya dates project (ADR 0010): all issues, decisions, product docs, plans, research — and the project's Claude Code skills, served from this repo as a plugin marketplace. Skills are then invocable anywhere, namespaced: /maya:maya-orient, /maya:maya-plan, and so on. See plugins/maya/skills/README.md for what each does and how they chain. Skills change only via a commit here plus a version bump in plugins/maya/.claude-plugin/plugin.json. Seven kinds of artifact. Four live as files in this repo, three as issues. Every skill acts at exactly one place in this flow — skills are the verbs, artifacts are the nouns. maya-orient is the exception: it reads everything and writes nothing (run it at session start). Rounded nodes are skills; rectangles are artifacts. Not shown: maya-orient (reads all of it), and maya-implement, which is not a step but the rulebook every dispatched agent — and every hand-made change — works under between dispatch and PR.
README
以下は原文 README の抜粋です。原文を見る。
maya-project
Project management hub for the Maya dates project (ADR 0010): all issues, decisions, product docs, plans, research — and the project’s Claude Code skills, served from this repo as a plugin marketplace.
Install the skills
/plugin marketplace add drewsonne/maya-project
/plugin install maya@maya-project
Skills are then invocable anywhere, namespaced: /maya:maya-orient,
/maya:maya-plan, and so on. See plugins/maya/skills/README.md for what
each does and how they chain. Skills change only via a commit here plus a
version bump in plugins/maya/.claude-plugin/plugin.json.
The artifacts, and how work flows between them
Seven kinds of artifact. Four live as files in this repo, three as issues.
| artifact | lives in | what it is | written by |
|---|---|---|---|
| Research | docs/research/ |
A sourced fact about the world — a published date pair, a convention in the literature, a disagreement between authors. Never a choice. | maya-record |
| ADR | docs/decisions/ |
A choice that constrains the code, made by the Maintainer. Numbered, never rewritten — superseded by a later ADR. | maya-record |
| Product | docs/product/ |
The PRD: who the product is for and what it must get right. Outcomes, never technologies. | maya-spec (interview) |
| Plan | docs/plan/ |
Waves of work packages decomposed from stories — scope, contract, criteria, fixtures per package. | maya-plan |
| Epic | issue, label epic |
A PRD outcome, long-lived. Few. Carries stories, never tasks directly. | maya-plan / by hand |
| Story | issue, label story, sub-issue of an epic |
One outcome with acceptance criteria. The backlog — unbounded (ADR 0011). | anyone, any time |
| Task | issue, type Task, sub-issue of a story |
One work package verbatim: one agent, one branch, one PR. Just-in-time only. | maya-plan |
Every skill acts at exactly one place in this flow — skills are the verbs,
artifacts are the nouns. maya-orient is the exception: it reads everything
and writes nothing (run it at session start).
flowchart TD
SPEC([maya-specinterviews the Maintainer— gate G1]) --> P[Product PRDdocs/product]
REC([maya-record]) --> R[Researchdocs/research]
REC --> A[ADRdocs/decisions]
R -->|"finding first, then adecision that cites it"| A
P -->|each outcome| E[Epic]
E --> ST[Storyunbounded backlog]
ST -->|"gate G2: Maintainer appliesthe authorized label"| PLAN([maya-plandecomposes, justifiedby PRD + ADRs])
A --> PLAN
PLAN --> PL[Plandocs/plan]
PL -->|"wave in flight + 1 only"| T[Task]
R -->|sourced vectors| FIX([maya-fixturesbuilds the correctness suitein maya-date-fixtures])
FIX -->|"suite must exist and pass —gates arithmetic planningand every dispatch"| FLEET
T --> FLEET([maya-fleetpreflight, dispatch one wave,each agent undermaya-implement rules])推奨ツール
別のキーワードを試すか、フィルタを外してください。
インストール
npx skillfish add drewsonne/maya-project