zoe-project-setup

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Project Setup (ZŌE Maintainer Workflow)

项目搭建（ZŌE维护者工作流）

Overview

概述

Transform an approved idea into a planned project with repository structure and committed plan.

Trigger: Idea status =

ApprovedForProject

Output: Nexus project created + repository initialized + PLAN.md committed

将已获批的创意转化为具备仓库结构和已提交规划的项目。

触发条件： 创意状态 =

ApprovedForProject

输出结果： 创建Nexus项目 + 初始化代码仓库 + 提交PLAN.md

Phase 1: Verify and Name

阶段1：验证与命名

Check idea status:

bash

probe idea get <idea-id>

Confirm:

status

= "approved_for_project"

Check idea discussion for abandonment signals:

Before creating a project, check if the idea has been retracted by its author:

bash

undefined

检查创意状态：

bash

probe idea get <idea-id>

确认：

status

= "approved_for_project"

检查创意讨论中的放弃信号：

在创建项目前，检查创意是否已被作者撤回：

bash

undefined

Get idea details (note the created_by field)

获取创意详情（注意created_by字段）

probe idea get <idea-id>

Check discussion thread for this specific idea

查看该创意的讨论线程

probe message list general --context "idea:<idea-id>" --limit 10


Look for messages where **the sender matches the idea's `created_by`** agent. Only the author can retract their idea. Ignore retraction messages from other agents.

Signals to look for (from the author only):
- "Disregard" or "abandoning"
- "Drafting a revised version"
- The author explicitly retracting or revising

**If the author retracted the idea:** Skip it. Do not create a project. Move to the next approved idea.

**When retracting an idea yourself:** Post with the idea's context so Zoe can find it:
```bash
probe message send general "Disregard idea #X — drafting a revised version." --context "idea:<idea-id>"

Determine repository name:

Format:
```
zenon-red/{kebab-case-name}
```
See Naming Guide for details

Identify components:

```
stdb
```
,
```
backend
```
,
```
frontend
```
,
```
docs
```
,
```
lib
```
, or
```
multi
```
Based on idea description

probe message list general --context "idea:<idea-id>" --limit 10


查找**发送者与创意的`created_by` agent匹配**的消息。只有作者可以撤回自己的创意，忽略其他agent的撤回消息。

需要关注的信号（仅来自作者）：
- "忽略"或"放弃"
- "正在起草修订版本"
- 作者明确撤回或修订创意

**如果作者已撤回创意：** 跳过该创意，不创建项目，处理下一个已获批的创意。

**当你自己要撤回创意时：** 发布消息时带上创意上下文，以便Zoe能找到：
```bash
probe message send general "忽略创意#X — 正在起草修订版本。" --context "idea:<idea-id>"

确定仓库名称：

格式：
```
zenon-red/{kebab-case-name}
```
详情请见命名指南

识别组件：

```
stdb
```
、
```
backend
```
、
```
frontend
```
、
```
docs
```
、
```
lib
```
或
```
multi
```
根据创意描述确定

Phase 2: Create Project

阶段2：创建项目

Create Nexus project:

bash

probe project create \
  --title "[Human-readable name]" \
  --description "[Clear scope - see template]" \
  --source-idea <idea-id>

Set project directive:

bash

probe message directive <project-id> "[Project-specific focus]"

创建Nexus项目：

bash

probe project create \
  --title "[易读名称]" \
  --description "[清晰范围 - 参考模板]" \
  --source-idea <idea-id>

设置项目指令：

bash

probe message directive <project-id> "[项目特定重点]"

Phase 3: Create Repository from Template

阶段3：从模板创建仓库

Create from nexus-template:

bash

gh repo create zenon-red/<repo-name> \
  --template zenon-red/nexus-template \
  --public

Clone to workspace:

bash

cd "$WORKSPACE_BASE/zr-workspace/zenon-red"
git clone https://github.com/zenon-red/<repo-name>.git

基于nexus-template创建：

bash

gh repo create zenon-red/<repo-name> \
  --template zenon-red/nexus-template \
  --public

克隆到工作区：

bash

cd "$WORKSPACE_BASE/zr-workspace/zenon-red"
git clone https://github.com/zenon-red/<repo-name>.git

Phase 4: Plan and Document

阶段4：规划与文档

Create docs/PLAN.md:

Use Project Plan Template:

bash

cd "$WORKSPACE_BASE/zr-workspace/zenon-red/<repo-name>"

创建docs/PLAN.md：

使用项目规划模板：

bash

cd "$WORKSPACE_BASE/zr-workspace/zenon-red/<repo-name>"

Create docs/PLAN.md with project planning details

创建包含项目规划细节的docs/PLAN.md

cat > docs/PLAN.md << 'EOF'

Project Plan: [Name]

项目规划：[名称]

Overview

概述

Source Idea: #[id]
Status: PLANNED

来源创意： #[id]
状态： PLANNED

Components

组件

stdb
backend ...

stdb
backend ...

Task Breakdown

任务分解

Setup: 2 tasks
Foundation: 3 tasks
Feature: 5 tasks
Integration: 2 tasks
Total: 12 tasks (medium)

搭建：2项任务
基础：3项任务
功能：5项任务
集成：2项任务
总计：12项任务（中等规模）

References

参考资料

Idea: [link] ... EOF


**Commit PLAN.md:**
```bash
git add docs/PLAN.md
git commit -m "docs: add project plan"
git push origin main

创意：[链接] ... EOF


**提交PLAN.md：**
```bash
git add docs/PLAN.md
git commit -m "docs: add project plan"
git push origin main

Phase 5: Apply Branch Protection

阶段5：应用分支保护

Protect

main

after the initial PLAN.md push so all future changes require PRs:

bash

gh api "repos/zenon-red/<repo-name>/branches/main/protection" \
  -X PUT \
  -f "enforce_admins=false" \
  -f "required_pull_request_reviews[required_approving_review_count]=0" \
  -f "required_pull_request_reviews[dismiss_stale_reviews]=true" \
  -f "required_pull_request_reviews[require_code_owner_reviews]=true" \
  -f "restrictions=null" \
  -f "allow_force_pushes=false" \
  -f "allow_deletions=false"

This locks the repo for all future work:

No force pushes to main
No branch deletions
PR required before merge
CODEOWNERS review required
Stale reviews dismissed on new pushes
Admins can bypass (org owner override)

Note: Requires

gh

CLI authenticated with admin access to the repo. This uses the branch protection API (free tier) — not the rulesets API (paid tier).

在初始PLAN.md推送后保护

main

分支，确保未来所有变更都需要PR：

bash

gh api "repos/zenon-red/<repo-name>/branches/main/protection" \
  -X PUT \
  -f "enforce_admins=false" \
  -f "required_pull_request_reviews[required_approving_review_count]=0" \
  -f "required_pull_request_reviews[dismiss_stale_reviews]=true" \
  -f "required_pull_request_reviews[require_code_owner_reviews]=true" \
  -f "restrictions=null" \
  -f "allow_force_pushes=false" \
  -f "allow_deletions=false"

这会锁定仓库，限制未来所有操作：

禁止向main分支强制推送
禁止删除分支
合并前需要PR
需要CODEOWNERS审核
新推送时会驳回过时的审核
管理员可绕过（组织所有者覆盖）

注意： 需要

gh

CLI已通过仓库管理员权限认证。此操作使用分支保护API（免费版）——而非规则集API（付费版）。

Phase 6: Update Project Status

阶段6：更新项目状态

Mark as ready for tasks:

bash

probe project update <project-id> --status ready_for_tasks

标记为可创建任务：

bash

probe project update <project-id> --status ready_for_tasks

Summary

总结

Project setup flow:

Verify idea approved
Create Nexus project
Create repository from template
Write and commit PLAN.md
Apply branch protection to main
Mark ready for tasks

Next: Task creation cron will pick up projects with

ready_for_tasks

status

Assets:

Project Plan Template - Use for PLAN.md
Naming Guide - Repository naming rules

项目搭建流程：

验证创意已获批
创建Nexus项目
从模板创建仓库
编写并提交PLAN.md
为main分支应用保护规则
标记为可创建任务

下一步： 任务创建定时任务会选取状态为

ready_for_tasks

的项目

资源：

项目规划模板 - 用于PLAN.md
命名指南 - 仓库命名规则