stackflow
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseStackflow
Stackflow
Stackflow is a Goose-compatible Agent Skill for disciplined software delivery. It is installed as one skill and provides slash-style command aliases for each stage of the workflow.
Stackflow 是一款兼容Goose的Agent Skill，用于规范化软件交付。它作为单个技能安装，为工作流的每个阶段提供斜杠式命令别名。
Core Principle
核心原则
Stackflow combines two complementary disciplines:
- Gstack-style judgment: decide what matters, challenge weak scope, review adversarially, and ship with practical confidence.
- Superpowers-style execution: write plans, use TDD, debug systematically, verify before completion, and preserve clean handoffs.
Do not treat the coding agent as an omnipotent genie. Divide work into clear stages:
- Decision — validate the idea, clarify PMF, challenge scope, and record major decisions.
- Planning — turn approved scope into a technical plan, context map, and atomic tasks.
- Execution — implement with TDD, focused tasks, code review, debugging discipline, QA, and release handoff.
Stackflow 结合了两种互补的方法：
- Gstack式判断：确定关键事项、质疑不合理范围、进行对抗性评审，并带着务实的信心交付产品。
- Superpowers式执行：制定计划、采用TDD、系统化调试、完成前验证，并保持清晰的交接。
不要将编码Agent视为无所不能的精灵。将工作划分为清晰的阶段：
- 决策 — 验证想法、明确PMF、质疑范围，并记录重大决策。
- 规划 — 将获批的范围转化为技术方案、上下文图谱和原子任务。
- 执行 — 通过TDD、聚焦任务、代码评审、规范化调试、QA及发布交接来落地实现。
Command Aliases
命令别名
When the user starts a prompt with one of these aliases, treat it as a Stackflow command and follow the matching command file under .
commands/| Command alias | Command file | Purpose |
|---|---|---|
| | Product strategy, PMF validation, edge cases, design doc |
| | Ruthless CEO-style scope challenge |
| | Engineering review, context map, atomic task plan |
| | Fast-track combined strategy/design/engineering planning |
| | TDD execution engine |
| | Evidence-based debugging clinic |
| | Code quality and adversarial security review |
| | UI/E2E QA exploration |
| | Final verification, release, and PR handoff |
当用户的提示以以下别名之一开头时，将其视为Stackflow命令，并遵循目录下对应的命令文件。
commands/| 命令别名 | 命令文件 | 用途 |
|---|---|---|
| | 产品策略、PMF验证、边缘案例、设计文档 |
| | 类似CEO风格的严苛范围质疑 |
| | 工程评审、上下文图谱、原子任务计划 |
| | 快速整合策略/设计/工程规划 |
| | TDD执行引擎 |
| | 基于证据的调试指导 |
| | 代码质量与对抗性安全评审 |
| | UI/E2E QA探索 |
| | 最终验证、发布及PR交接 |
How to Use
使用方法
Install the skill once, then use the command aliases directly in Goose prompts.
stackflowExamples:
text
/sf-think I want to build a real-time multiplayer cursor tracker.text
/sf-plan Read design-doc.md, consider existing ADRs, create a context map, and write task.md.text
/sf-build Implement task.md using strict RED-GREEN-REFACTOR TDD.只需安装一次技能，即可在Goose提示中直接使用命令别名。
stackflow示例：
text
/sf-think I want to build a real-time multiplayer cursor tracker.text
/sf-plan Read design-doc.md, consider existing ADRs, create a context map, and write task.md.text
/sf-build Implement task.md using strict RED-GREEN-REFACTOR TDD.Artifacts
产出物
When appropriate, create or update local project artifacts:
- — validated product and solution blueprint
design-doc.md - — ADR-style long-term decisions
.stackflow/decisions/NNNN-short-name.md - — concise repository context map, preferably signatures and structure rather than full file bodies
.stackflow-context.md - — atomic implementation tasks
task.md - QA/review/debug reports as Markdown when useful
在合适的情况下，创建或更新本地项目产出物：
- — 经过验证的产品与解决方案蓝图
design-doc.md - — ADR风格的长期决策记录
.stackflow/decisions/NNNN-short-name.md - — 简洁的仓库上下文图谱，优先记录签名和结构而非完整文件内容
.stackflow-context.md - — 原子化实现任务
task.md - 必要时生成Markdown格式的QA/评审/调试报告
Safety and Constraints
安全与约束
- Do not write production code during decision or planning commands unless the user explicitly switches to execution.
- Do not invent requirements, benchmarks, security claims, or test results.
- Prefer small, verifiable steps over broad rewrites.
- For implementation, write or update tests before production code whenever feasible.
- Do not commit, push, merge, or open PRs unless the user explicitly asks.
- Use Goose-available tools and normal repository files. Do not assume external runtime-specific commands or paths.
- 在决策或规划命令阶段，除非用户明确切换到执行阶段，否则不要编写生产代码。
- 不要凭空编造需求、基准、安全声明或测试结果。
- 优先选择小型、可验证的步骤，而非大范围重写。
- 对于实现工作，只要可行，就在编写生产代码之前先编写或更新测试。
- 除非用户明确要求，否则不要提交、推送、合并或创建PR。
- 使用Goose可用的工具和常规仓库文件。不要假设外部运行时特定的命令或路径。
References
参考资料
This port includes selected process references from Gstack and Superpowers under:
references/gstack/references/superpowers/
Use them as supporting material when a command asks for deeper process guidance.
此移植版本包含选自Gstack和Superpowers的部分流程参考资料，存放于：
references/gstack/references/superpowers/
当命令需要更深入的流程指导时，可将其作为支持材料使用。