Back to Details

sprint-forge

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Sprint Forge

Sprint Forge

Assets

资源

This skill uses a modular assets architecture. Detailed workflows, helpers, and templates are in the assets/ directory:
  • assets/modes/ — INIT, SPRINT, and STATUS mode workflows
  • assets/helpers/ — Analysis guide, debt tracker, sprint generator, re-entry generator
  • assets/templates/ — Roadmap, sprint, project README, and re-entry prompt templates
See assets/README.md for full directory documentation.
本Skill采用模块化资源架构。详细的工作流、辅助工具和模板位于assets/目录中：
  • assets/modes/ — INIT、SPRINT和STATUS模式的工作流
  • assets/helpers/ — 分析指南、债务追踪器、冲刺生成器、重入提示生成器
  • assets/templates/ — 路线图、冲刺、项目README和重入提示模板
完整的目录文档请查看assets/README.md。

Purpose

目标

Sprint Forge is an adaptive sprint workflow skill designed for iterative project execution. Unlike rigid planners that pre-generate all sprints upfront, Sprint Forge:
  • Analyzes first — deep exploration of the project/issue before committing to a plan
  • Generates sprints one at a time — each sprint feeds from the previous one's retro, recommendations, and accumulated debt
  • Tracks debt formally — an accumulated debt table that persists across sprints and never loses items
  • Adapts the roadmap — the plan evolves based on what execution reveals
  • Persists context — re-entry prompts allow a new agent (or new session) to recover full context
This skill works for any project type, language, or framework.
Sprint Forge是一款专为迭代项目执行设计的自适应冲刺工作流Skill。与预先生成所有冲刺的僵化规划工具不同，Sprint Forge具备以下特性：
  • 先分析 — 在制定计划前深度探索项目/问题
  • 逐个生成冲刺 — 每个冲刺都基于上一个冲刺的回顾总结、建议以及累积的技术债务生成
  • 规范化追踪债务 — 跨冲刺持久保存的累积技术债务表，不会丢失任何条目
  • 动态演进路线图 — 根据执行过程中的发现更新计划
  • 上下文持久化 — 重入提示允许新Agent或新会话恢复完整上下文，无缝继续工作
本Skill适用于任何项目类型、编程语言或框架。

Critical Rules

核心规则

RULE 1 — SPRINT-BY-SPRINT
Sprints are generated ONE AT A TIME. Never pre-generate all sprints. Each sprint is informed by the previous sprint's retro, recommendations, and accumulated debt. This ensures the plan adapts to reality.
RULE 2 — SUGGESTED PHASES, NOT RIGID
The roadmap defines suggested phases per sprint. During execution, emergent phases MUST be added when new findings surface. Phases are guidelines, not constraints.
RULE 3 — RETRO IS FORMAL INPUT
The retrospective and recommendations from Sprint N-1 are formal input for Sprint N. Every recommendation must either become a task in the next sprint or have its deferral justified in the Disposition table.
RULE 4 — DEBT NEVER DISAPPEARS
The Accumulated Technical Debt table is inherited sprint to sprint. An item is only closed when explicitly resolved. Items are never deleted — only their status changes.
RULE 5 — ADAPTIVE
The roadmap is a living document. If execution reveals that a planned sprint no longer makes sense, the roadmap is updated. The plan serves execution, not the reverse.
RULE 6 — LANGUAGE-AGNOSTIC
This skill works for any language, framework, or project type. It does not assume Flutter, React, Dart, or any specific technology. The analysis determines the structure.
RULE 7 — CONTEXT PERSISTENCE
After INIT and after each executed sprint, re-entry prompts are updated. These prompts allow any agent in any session to recover full project context and continue seamlessly.
规则1 — 逐个冲刺
冲刺必须逐个生成。绝不能预先生成所有冲刺。每个冲刺都需参考上一个冲刺的回顾总结、建议以及累积的技术债务。这确保计划能够适应实际情况。
规则2 — 建议阶段而非强制约束
路线图为每个冲刺定义了建议阶段。在执行过程中，若有新发现，必须添加新的阶段。阶段是指导方针，而非约束条件。
规则3 — 回顾总结为正式输入
第N-1个冲刺的回顾总结和建议是第N个冲刺的正式输入。每条建议要么成为下一个冲刺的任务，要么在处置表中说明推迟的理由。
规则4 — 债务永不消失
累积技术债务表会在冲刺间继承。只有当条目被明确解决时才会标记为已关闭。条目绝不会被删除——仅更新其状态。
规则5 — 自适应
路线图是一份活文档。如果执行过程显示原计划的冲刺不再合理，则更新路线图。计划为执行服务，而非相反。
规则6 — 语言无关
本Skill适用于任何语言、框架或项目类型。不会假设使用Flutter、React、Dart或任何特定技术。分析过程将决定结构。
规则7 — 上下文持久化
在INIT模式完成后以及每个冲刺执行完成后，都会更新重入提示。这些提示允许任何会话中的任何Agent恢复完整的项目上下文并无缝继续工作。

Capabilities Matrix

能力矩阵

CapabilityINITSPRINTSTATUS
Analyze codebase/projectYesNoNo
Create vault structureYesNoNo
Generate roadmapYesNoNo
Generate/update re-entry promptsYesYesNo
Generate sprintNoYesNo
Execute sprint tasksNoYesNo
Write/modify codeNoYesNo
Read vault/sprintsYesYesYes
Update accumulated debtNoYesNo
Report progressNoNoYes
能力INITSPRINTSTATUS
分析代码库/项目是否否
创建存储库结构是否否
生成路线图是否否
生成/更新重入提示是是否
生成冲刺否是否
执行冲刺任务否是否
编写/修改代码否是否
读取存储库/冲刺内容是是是
更新累积技术债务否是否
报告进度否否是

Mode Detection

模式检测

ModeEN SignalsES SignalsWhat It Does
INIT"analyze", "audit", "start project", "create roadmap""analiza", "audita", "inicia proyecto", "crea roadmap"Analyzes the project, generates findings, creates roadmap, scaffolds vault, generates re-entry prompts
SPRINT"generate sprint", "next sprint", "execute sprint""genera sprint", "siguiente sprint", "ejecuta sprint"Generates the next sprint from roadmap + previous sprint + debt, optionally executes it
STATUS"project status", "progress", "technical debt""estado del proyecto", "progreso", "deuda técnica"Reports completed sprints, accumulated debt, metrics, next sprint preview
Disambiguation: If the user's intent is unclear, ask:
"Do you want me to analyze the project (INIT), generate/execute the next sprint (SPRINT), or check project status (STATUS)?"
模式英文触发词西班牙文触发词功能
INIT"analyze", "audit", "start project", "create roadmap""analiza", "audita", "inicia proyecto", "crea roadmap"分析项目、生成分析结果、创建路线图、搭建存储库结构、生成重入提示
SPRINT"generate sprint", "next sprint", "execute sprint""genera sprint", "siguiente sprint", "ejecuta sprint"根据路线图+上一个冲刺+技术债务生成下一个冲刺，可选择执行
STATUS"project status", "progress", "technical debt""estado del proyecto", "progreso", "deuda técnica"报告已完成的冲刺、累积的技术债务、指标以及下一个冲刺预览
歧义处理：如果用户意图不明确，请询问：
"你希望我分析项目（INIT模式）、生成/执行下一个冲刺（SPRINT模式），还是查看项目状态（STATUS模式）？"

Quick Start

快速开始

INIT Mode

INIT模式

Use when starting a new project workflow:
Analyze this project and create a roadmap for the refactoring work.
This will: explore the codebase, generate findings, create an adaptive roadmap, scaffold the output directory, and generate re-entry prompts.
Full workflow: See assets/modes/INIT.md
启动新项目工作流时使用：
Analyze this project and create a roadmap for the refactoring work.
这将：探索代码库、生成分析结果、创建自适应路线图、搭建输出目录结构，并生成重入提示。
完整工作流： 查看assets/modes/INIT.md

SPRINT Mode

SPRINT模式

Use when ready to work on the next sprint:
Generate the next sprint.
Or to generate and immediately execute:
Generate and execute the next sprint.
This will: read the roadmap and previous sprint, build the disposition table, generate phases, and optionally execute task by task.
Full workflow: See assets/modes/SPRINT.md
准备进行下一个冲刺时使用：
Generate the next sprint.
或生成并立即执行：
Generate and execute the next sprint.
这将：读取路线图和上一个冲刺内容、构建处置表、生成阶段，可选择逐个执行任务。
完整工作流： 查看assets/modes/SPRINT.md

STATUS Mode

STATUS模式

Use to check project progress:
Show me the project status and technical debt.
This will: read all sprints, calculate metrics, display progress and accumulated debt.
Full workflow: See assets/modes/STATUS.md
查看项目进度时使用：
Show me the project status and technical debt.
这将：读取所有冲刺内容、计算指标、展示进度和累积技术债务。
完整工作流： 查看assets/modes/STATUS.md

Integration with Other Skills

与其他Skill的集成

SkillIntegration
obsidian
INIT: Use SYNC mode to save findings and roadmap to vault. SPRINT: Use SYNC to update sprint files. STATUS: Use READ to access vault data. Falls back to filesystem if MCP is not available.
code-analyzer
INIT: Can be used as a preliminary step. The code-analyzer reports feed into Sprint Forge findings, providing structured technical input for the roadmap.
Skill集成方式
obsidian
INIT模式：使用SYNC模式将分析结果和路线图保存到存储库。SPRINT模式：使用SYNC模式更新冲刺文件。STATUS模式：使用READ模式访问存储库数据。如果MCP不可用，则回退到文件系统。
code-analyzer
INIT模式：可作为初步步骤使用。code-analyzer的报告将作为Sprint Forge分析结果的输入，为路线图提供结构化的技术信息。

Limitations

局限性

  1. Mode boundary: Each mode has specific capabilities — INIT cannot execute code, SPRINT cannot create roadmaps, STATUS cannot modify files
  2. One sprint at a time: By design, you cannot generate multiple sprints in advance
  3. Requires analysis first: SPRINT mode expects INIT to have been run — it needs a roadmap and findings
  4. Manual execution: Sprint tasks are executed by the agent, not automated CI/CD
  5. Context window: For projects with many sprints (>5), use separate sessions per sprint. Re-entry prompts ensure continuity.
  6. No automated validation: Cannot verify that the roadmap matches codebase reality — relies on thorough analysis during INIT
  7. External blockers: Cannot resolve dependencies on external teams — logs them as blocked tasks and moves on
  8. Debt resolution: Debt items require explicit action to close — they don't auto-resolve
  1. 模式边界：每个模式都有特定能力——INIT模式无法执行代码，SPRINT模式无法创建路线图，STATUS模式无法修改文件
  2. 逐个冲刺：设计上不允许提前生成多个冲刺
  3. 需先完成分析：SPRINT模式要求已运行INIT模式——需要路线图和分析结果
  4. 手动执行：冲刺任务由Agent执行，而非自动化CI/CD
  5. 上下文窗口：对于包含多个冲刺（>5个）的项目，每个冲刺使用单独的会话。重入提示可确保连续性。
  6. 无自动验证：无法验证路线图是否与代码库实际情况匹配——依赖INIT模式期间的全面分析
  7. 外部阻塞：无法解决依赖外部团队的问题——将其记录为阻塞任务并继续后续工作
  8. 债务解决：技术债务条目需要明确操作才能关闭——不会自动解决

Version History

版本历史

VersionDateChanges
1.02026-02-16Initial release — INIT, SPRINT, STATUS modes. Adaptive roadmap, formal debt tracking, re-entry prompts, language-agnostic design.
版本日期变更
1.02026-02-16初始版本——包含INIT、SPRINT、STATUS模式。自适应路线图、规范化技术债务追踪、重入提示、语言无关设计。