MCP Setup (Default Required)
Install (always use latest):
CODEBLOCK0
INLINECODE0 must be kept up to date — outdated versions may be missing tools or contain bugs.
Key methods:
- - Discovery:
projectLocate / projectScan / INLINECODE3 - Context:
projectContext / taskList / taskContext / INLINECODE7 - Execution: INLINECODE8
- Planning:
taskCreate / INLINECODE10
Init: Repo Governance Setup
When .projitive/ does not exist or is incomplete, call projectInit(projectPath="<project-dir>") immediately. Do NOT ask the user to do this manually.
Mandatory Governance Files
- -
README.md — scope, glossary, required reading - INLINECODE14 — stage goals and milestones
- INLINECODE15 — task pool with status + evidence
- INLINECODE16 — design decisions and rationale
- INLINECODE17 — execution reports and evidence
- INLINECODE18 — per-tool response templates
Execution Loop
- 1.
taskNext — pick actionable task - INLINECODE20 — get evidence and hints
- Execute; update
designs/ and INLINECODE22 - INLINECODE23 — verify alignment
- Repeat
If taskNext returns empty: projectContext → roadmapContext → taskCreate 1–3 focused TODOs (+ roadmapCreate if needed) → taskNext.
Task Status Rules
- -
TODO → IN_PROGRESS: execution started, scope clear - INLINECODE32 →
DONE: evidence exists, criteria met - INLINECODE34 →
BLOCKED: external dependency blocks progress - INLINECODE36 →
TODO/IN_PROGRESS: after blocker resolution is documented
Never mark DONE without evidence references.
Evidence Rules
- - Design rationale → INLINECODE39
- Execution outcome → INLINECODE40
- Task updates must reference exact evidence files
Always-on Rules
- - Resolve governance root before any task decisions
- Governance state writes MUST go through MCP tools; never directly edit
tasks.md/ INLINECODE42 - Keep status transitions explicit and evidence-linked
- Preserve ID stability in roadmap/tasks/designs/reports
- Prefer smallest valid step that moves one task forward
Fallback (no MCP)
- 1. Find nearest INLINECODE43
- Read
README.md + roadmap.md + INLINECODE46 - Execute one narrow task
- Write evidence to
designs/ or INLINECODE48 - Update task status in INLINECODE49
MCP 设置（默认必需）
安装（始终使用最新版本）：
bash
npm install -g @projitive/mcp@latest
@projitive/mcp 必须保持最新——过时的版本可能会缺少工具或包含错误。
关键方法：
- - 发现：projectLocate / projectScan / projectNext
- 上下文：projectContext / taskList / taskContext / roadmapContext
- 执行：taskNext
- 规划：taskCreate / roadmapCreate
初始化：仓库治理设置
当 .projitive/ 不存在或不完整时，立即调用 projectInit(projectPath=<项目目录>)。不要要求用户手动执行此操作。
强制性治理文件
- - README.md — 范围、术语表、必读内容
- roadmap.md — 阶段目标和里程碑
- tasks.md — 带状态和证据的任务池
- designs/ — 设计决策和理由
- reports/ — 执行报告和证据
- templates/ — 每个工具对应的响应模板
执行循环
- 1. taskNext — 选取可执行的任务
- taskContext — 获取证据和提示
- 执行；更新 designs/ 和 reports/
- taskContext — 验证对齐情况
- 重复
如果 taskNext 返回空：projectContext → roadmapContext → 创建 1–3 个聚焦的待办事项（如有需要则加上 roadmapCreate）→ taskNext。
任务状态规则
- - TODO → INPROGRESS：开始执行，范围明确
- INPROGRESS → DONE：存在证据，满足标准
- INPROGRESS → BLOCKED：外部依赖阻碍进展
- BLOCKED → TODO/INPROGRESS：在记录阻塞解决后
没有证据引用时，切勿标记为 DONE。
证据规则
- - 设计理由 → .projitive/designs/
- 执行结果 → .projitive/reports/
- 任务更新必须引用确切的证据文件
始终生效的规则
- - 在任何任务决策之前，先解决治理根目录问题
- 治理状态写入必须通过 MCP 工具；切勿直接编辑 tasks.md/roadmap.md
- 保持状态转换明确，并与证据关联
- 保持路线图/任务/设计/报告中 ID 的稳定性
- 优先选择能推动一个任务前进的最小有效步骤
备用方案（无 MCP）
- 1. 找到最近的 .projitive/
- 读取 README.md + roadmap.md + tasks.md
- 执行一个狭窄的任务
- 将证据写入 designs/ 或 reports/
- 更新 tasks.md 中的任务状态
