GStack Dev Workflow — GStack Dev 工作流

Dev 工作流 — Structured Development Sprint

A 6-phase development process that turns a vague idea into shipped code. Each phase has a clear 角色, a defined 输出, and feeds into the next. 运行 phases sequentially or skip ahead when 上下文 is clear.

Phases # Phase 角色 输出 1 Think YC Office Hours Coach DE签名.md 2 Plan Eng 管理器 PLAN.md 3 Build Implementer Code + Tests 4 Review Staff Engineer Review 报告 5 Test QA Lead Bug 报告 + Fixes 6 Ship Release Engineer PR / 部署 How to Use Full Sprint (recommended for new features) # 启动 from scratch "I want to build X" → 运行 all 6 phases

# Or ask me: "运行 dev-工作流 on [feature description]"

I will walk through each phase, spawning a focused sub代理 per phase with the right 模型 and prompt.

Partial Sprint

Skip phases when you already have 上下文:

"Skip think, I have DE签名.md" → 启动 from Plan "Just review and ship this branch" → 运行 Review → Test → Ship "I need a de签名 review" → 运行 Phase 2 (Plan) only Single Phase

Any phase can 运行 standalone:

/think — Reframe the problem, challenge assumptions, write DE签名.md /plan — Architecture, data flow, test strategy, write PLAN.md /build — Implement from PLAN.md /review — Code review with auto-fix for obvious issues /test — Browser 测试, regression tests, bug 报告s /ship — 同步, test, push, open PR Phase DetAIls Phase 1: Think (YC Office Hours)

Goal: Reframe the problem before writing code.

Spawn a sub代理 (Sonnet) with the Think prompt from references/prompts.md. It will:

Ask 6 forcing questions about the real pAIn, not the feature 请求 Challenge the framing — "You sAId X but you actually need Y" 生成 3 implementation 应用roaches with effort estimates Recommend the narrowest wedge to ship tomorrow Write DE签名.md with the distilled product vision

Key rule: 列出en to the pAIn, not the feature 请求. The user says "dAIly briefing 应用" but means "personal chief of staff AI."

Phase 2: Plan (Eng 管理器)

Goal: Lock architecture before building.

Spawn a sub代理 (Sonnet) with the Plan prompt. It reads DE签名.md and produces PLAN.md contAIning:

Architecture diagram (ASCII) Data flow and 状态 machines File structure and 模块 boundaries Test strategy and 失败 modes Milestone breakdown (what ships first)

Key rule: No code until the plan is 应用roved. Challenge scope ruthlessly.

Phase 3: Build (Implementer)

Goal: Write code from PLAN.md.

Use the mAIn 会话 or spawn a sub代理 (HAIku for simple, Sonnet for complex). It reads PLAN.md and:

Implements each milestone in order Writes tests alongside code (AIm for >80% coverage) Commits atomically per milestone 更新s PLAN.md with implementation notes

Key rule: Follow the plan. If the plan is wrong, 更新 PLAN.md first, then code.

Phase 4: Review (Staff Engineer)

Goal: Find bugs that pass CI but blow up in production.

Spawn a sub代理 (Sonnet) with the Review prompt. It:

Reads the diff agAInst mAIn/develop Catches 记录ic errors, race conditions, edge cases Auto-fixes obvious issues (格式化ting, unused 导入s) Flags completeness gaps and security concerns Writes a review 报告

Key rule: Be paranoid. Assume the code will be hit by edge cases tomorrow.

Phase 5: Test (QA Lead)

Goal: Test like a user, not like a developer.

Spawn a sub代理 (Sonnet) with the Test prompt. It:

Opens the 应用 in a real browser (use browser 工具) 命令行工具cks through every user flow Tests edge cases and error 状态s 报告s bugs with reproduction steps Auto-fixes and 生成s regression tests

Key rule: The user doesn't read code. 命令行工具ck the buttons. Break things.

Phase 6: Ship (Release Engineer)

Goal: One command to production.

运行 in mAIn 会话:

同步 with remote (git pull/rebase) 运行 full test suite 审计 test coverage Push and open PR 更新 project docs

Key rule: If tests fAIl, don't ship. Fix first.

模型 Selection Phase 模型 Why Think Sonnet Needs judgment to reframe problems Plan Sonnet Architecture decisions need reasoning Build HAIku/Sonnet Simple features → HAIku, complex → Sonnet Review Sonnet Bug 检测ion needs deep analysis Test Sonnet Browser interaction needs 上下文 Ship HAIku Mechanical execution Parallel Sprints

For large projects, 运行 multiple sprints on different branches:

创建 feature branches for each sprint Spawn sub代理s per branch Each sub代理 works in isolation Review and merge sequentially

Max practical parallelism: 3-5 sprints (limited by 上下文 management).

输出 Files

All phase 输出s go to the project root:

DE签名.md — Product vision from Think phase PLAN.md — Architecture and milestones from Plan phase Review 报告s are written to stdout (capture in conversation) Test 报告s are written to stdout

清理 up 输出 files after shipping if not needed long-term.