alignfirst
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseAlignFirst Guide
AlignFirst 使用指南
Protocols
协议
Choose the appropriate protocol based on the task:
- Technical Specification (spec, or alspec): Read spec-protocol.md to write a technical specification
- Implementation Plans (plan, or alplan): Read plan-protocol.md to create implementation plans from a spec
- Align-and-Do Protocol (AAD): Read aad-protocol.md for smaller tasks without formal spec/plans
- Description (aldescription): Read description-protocol.md to write a description summarizing implemented work
根据任务选择合适的协议:
- 技术规范(spec,或称 alspec):阅读 spec-protocol.md 来编写技术规范
- 实施计划(plan,或称 alplan):阅读 plan-protocol.md 基于技术规范制定实施计划
- 对齐执行协议(AAD):阅读 aad-protocol.md,适用于无需正式规范/计划的小型任务
- 描述生成(aldescription):阅读 description-protocol.md 编写总结已完成工作的描述
TASK_DIR Location
TASK_DIR 位置
TASK_DIR is the directory where work files related to a task are stored. Usually, we use TASK_DIR = (a sub-directory of the folder). If no ticket ID is known, ask the user for it.
.plans/{TICKET_ID}/.plans- Create TASK_DIR if it doesn't exist
- Or, list existing files
TASK_DIR 是存储与任务相关的工作文件的目录。通常我们设置 TASK_DIR = ( 文件夹下的子目录)。如果不知道工单 ID,向用户询问。
.plans/{TICKET_ID}/.plans- 如果 TASK_DIR 不存在则创建
- 或者列出已存在的文件
File Naming Convention
文件命名规范
Format:
{CYCLE_LETTER}{FILE_NUMBER}-{FILE_TYPE}.mdCommon file types:
- - technical specification
spec - - implementation plan
plan - - AAD summary document
AAD.summary
Example structure:
text
.plans/
├── 123/
│ ├── A1-spec.md
│ ├── A2-plan.md
│ └── A3-AAD.summary.md
│ └── B1-spec.md格式:
{CYCLE_LETTER}{FILE_NUMBER}-{FILE_TYPE}.md常见文件类型:
- - 技术规范
spec - - 实施计划
plan - - AAD 总结文档
AAD.summary
示例结构:
text
.plans/
├── 123/
│ ├── A1-spec.md
│ ├── A2-plan.md
│ └── A3-AAD.summary.md
│ └── B1-spec.mdNotes
注意事项
- TICKET_ID is a unique identifier for the task, often an issue or ticket number.
- Cycles are identified by a CYCLE_LETTER (A, B, C...). The user decides when to start a new one.
- In a cycle, determine the next FILE_NUMBER from existing file names. Every new file must have a bumped file number.
- Do not bother the user with CYCLE_LETTER or FILE_NUMBER. They are for internal organization. It's up to you to list the files and determine the last CYCLE_LETTER and FILE_NUMBER. Start CYCLE_LETTER with if there is no existing cycle, and FILE_NUMBER with
A. So you just need to ask for a ticket ID if you don't have one.1 - When the user requests a new cycle: bump CYCLE_LETTER and reset FILE_NUMBER.
- There is no strict sequence of file types in the workflow. Available file types are also flexible; if you need a new one, just create it.
- TICKET_ID 是任务的唯一标识符,通常是 issue 或工单编号。
- 周期由 CYCLE_LETTER(A、B、C...)标识。用户决定何时开启新周期。
- 在一个周期内,根据现有文件名确定下一个 FILE_NUMBER。每个新文件的编号必须递增。
- 不要就 CYCLE_LETTER 或 FILE_NUMBER 打扰用户,这些是用于内部组织的。你需要自行列出文件,确定最新的 CYCLE_LETTER 和 FILE_NUMBER。如果没有现有周期,CYCLE_LETTER 从 开始,FILE_NUMBER 从
A开始。因此如果你没有工单 ID,只需要向用户询问即可。1 - 当用户要求开启新周期时:递增 CYCLE_LETTER 并重置 FILE_NUMBER。
- 工作流中没有严格的文件类型顺序。可用的文件类型也很灵活;如果你需要新的类型,直接创建即可。