feature-planning

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Feature Workflow: Plan Implementation

功能工作流：实施计划制定

YOU ARE READING THIS SKILL RIGHT NOW

你正在阅读此Skill

STOP. Before doing ANYTHING else:

☐ Create TodoWrite checklist (see below)
☐ Mark Step 1 as
```
in_progress
```
☐ Read CLAUDE.md first (if exists)

This skill is a WRAPPER that loads Z01 context and invokes superpowers:writing-plans

停止。在进行任何其他操作之前：

☐ 创建TodoWrite检查清单（见下文）
☐ 将步骤1标记为
```
in_progress
```
☐ 先阅读CLAUDE.md（如果存在）

此Skill是一个包装器，用于加载Z01上下文并调用superpowers:writing-plans

MANDATORY FIRST ACTION: Create TodoWrite

强制首要操作：创建TodoWrite

typescript

TodoWrite({
  todos: [
    {content: "Step 1: Load project context (CLAUDE.md if exists)", status: "in_progress", activeForm: "Reading CLAUDE.md"},
    {content: "Step 2: Verify Z01 files exist", status: "pending", activeForm: "Checking research"},
    {content: "Step 3: Read ALL Z01 files", status: "pending", activeForm: "Loading context"},
    {content: "Step 4: Invoke superpowers:writing-plans", status: "pending", activeForm: "Creating plan"},
    {content: "Step 5: Verify Z02 outputs", status: "pending", activeForm: "Validating output"}
  ]
})

After each step: Mark completed, move

in_progress

to next step.

typescript

TodoWrite({
  todos: [
    {content: "Step 1: Load project context (CLAUDE.md if exists)", status: "in_progress", activeForm: "Reading CLAUDE.md"},
    {content: "Step 2: Verify Z01 files exist", status: "pending", activeForm: "Checking research"},
    {content: "Step 3: Read ALL Z01 files", status: "pending", activeForm: "Loading context"},
    {content: "Step 4: Invoke superpowers:writing-plans", status: "pending", activeForm: "Creating plan"},
    {content: "Step 5: Verify Z02 outputs", status: "pending", activeForm: "Validating output"}
  ]
})

完成每一步后： 标记为已完成，将

in_progress

移至下一步。

Why Use This Wrapper?

为何使用此包装器？

Automates Z01 → Z02 file management
Loads CLAUDE.md constraints into planning context
Enforces feature-workflow naming conventions (Z02_{feature}_plan.md)
Integrates with clarification workflow (Z02_CLARIFY)
Maintains consistent file structure

Without this wrapper: You'd manually load Z01 files, pass to superpowers:writing-plans, manage Z02 output paths, check for clarifications.

自动化Z01 → Z02文件管理
将CLAUDE.md中的约束加载到计划制定上下文中
强制执行功能工作流命名规范（Z02_{feature}_plan.md）
与澄清工作流（Z02_CLARIFY）集成
保持一致的文件结构

如果不使用此包装器： 你需要手动加载Z01文件，传递给superpowers:writing-plans，管理Z02输出路径，检查是否需要澄清。

Workflow Steps

工作流步骤

Step 1: Load Project Context (MANDATORY FIRST)

步骤1：加载项目上下文（强制首要操作）

Read CLAUDE.md if it exists.

Extract from CLAUDE.md (if exists):

Mandatory patterns that MUST be preserved
Forbidden approaches to AVOID
Project conventions (naming, structure, etc.)
Release workflows and constraints

CRITICAL: If CLAUDE.md exists and contains constraints, these MUST be passed to superpowers:writing-plans so the plan preserves project standards.

如果CLAUDE.md存在，请阅读它。

从CLAUDE.md中提取（如果存在）：

必须保留的强制模式
需要避免的禁用方法
项目规范（命名、结构等）
发布工作流和约束

关键提示： 如果CLAUDE.md存在且包含约束，必须将这些约束传递给superpowers:writing-plans，以便计划符合项目标准。

Step 2: Verify Z01 Files Exist

步骤2：验证Z01文件是否存在

Scan for existing Z01 files in common locations (docs/ai/ongoing, .ai/ongoing, docs/ongoing).

If Z01 files found:

Note the ONGOING_DIR location
Extract feature name from filename (e.g., Z01_metrics_research.md → "metrics")
Feature name should already be sanitized snake_case from feature-research

If NO Z01 files found:

Ask user if they want to run feature-workflow:feature-researching first
Or proceed without research context (suboptimal)

扫描常见位置（docs/ai/ongoing、.ai/ongoing、docs/ongoing）中是否存在Z01文件。

如果找到Z01文件：

记录ONGOING_DIR的位置
从文件名中提取功能名称（例如：Z01_metrics_research.md → "metrics"）
功能名称应已通过feature-research处理为标准化的蛇形命名法（snake_case）

如果未找到Z01文件：

询问用户是否要先运行feature-workflow:feature-researching
或在没有研究上下文的情况下继续（不推荐）

Step 3: Read ALL Z01 Files

步骤3：读取所有Z01文件

Read all Z01 files in ONGOING_DIR:

Z01_{feature}_research.md (required)
Z01_CLARIFY_{feature}_research.md (if exists)

BLOCKING CHECK - If Z01_CLARIFY exists:

Read the file
Check if "User response:" fields are empty
If ANY empty → STOP, report: "Cannot plan with unanswered questions. Please answer all questions in Z01_CLARIFY_{feature}_research.md first."
If all answered → proceed

Extract:

Technical research and integration points
File paths and line ranges
Answered clarifications
Security and test requirements

读取ONGOING_DIR中的所有Z01文件：

Z01_{feature}_research.md（必填）
Z01_CLARIFY_{feature}_research.md（如果存在）

阻塞检查 - 如果Z01_CLARIFY存在：

读取文件
检查“User response:”字段是否为空
如果有任何空字段 → 停止并报告：“无法在存在未回答问题的情况下制定计划。请先回答Z01_CLARIFY_{feature}_research.md中的所有问题。”
如果所有问题都已回答 → 继续

提取内容：

技术研究和集成点
文件路径和行范围
已回答的澄清问题
安全和测试要求

Step 4: Invoke Superpowers Planning

步骤4：调用Superpowers计划制定功能

CRITICAL: This skill's primary job is to invoke superpowers:writing-plans with Z01 context. If you skip this invocation, the skill provides no value.

Use Skill tool to invoke

superpowers:writing-plans

Provide this instruction:

"Create an implementation plan for the {feature} feature based on the research in Z01_{feature}research.md and clarifications in Z01_CLARIFY{feature}_research.md.

MANDATORY CONSTRAINTS from CLAUDE.md: [Include any constraints, patterns, or forbidden approaches from CLAUDE.md here if it exists]

CRITICAL: Save the plan to {ONGOING_DIR}/Z02_{feature}_plan.md (use the detected path, NOT hardcoded docs/plans/).

The plan should be a DIRECTIVE document with:

Exact file paths from research
Complete code examples
Verification steps for each task
TDD structure (test-fail-implement-pass-commit)
Assumes engineer has minimal domain knowledge

If you discover NEW blocking questions during planning (not already in Z01_CLARIFY), create {ONGOING_DIR}/Z02_CLARIFY_{feature}_plan.md. Otherwise, do NOT create a Z02_CLARIFY file.

When incorporating answered questions: Delete fully-answered CLARIFY files or remove incorporated Q&A pairs if only some were answered."

关键提示： 此Skill的主要作用是加载Z01上下文并调用superpowers:writing-plans。如果跳过此调用，该Skill将毫无价值。

使用Skill工具调用

superpowers:writing-plans

提供以下指令：

“基于Z01_{feature}research.md中的研究内容和Z01_CLARIFY{feature}_research.md中的澄清信息，为{feature}功能创建实施计划。

来自CLAUDE.md的强制约束： [如果CLAUDE.md存在，请在此处包含其中的所有约束、模式或禁用方法]

关键提示：将计划保存到{ONGOING_DIR}/Z02_{feature}_plan.md（使用检测到的路径，而非硬编码的docs/plans/）。

该计划应为指导性文档，包含：

研究中提到的准确文件路径
完整的代码示例
每个任务的验证步骤
TDD结构（测试-失败-实现-通过-提交）
假设工程师具备最少的领域知识

如果在计划制定过程中发现新的阻塞问题（未包含在Z01_CLARIFY中），请创建{ONGOING_DIR}/Z02_CLARIFY_{feature}_plan.md。否则，请勿创建Z02_CLARIFY文件。

整合已回答的问题时： 删除已完全回答的CLARIFY文件，或如果仅部分问题已回答，则移除已整合的问答对。”

Step 5: Verify Outputs

步骤5：验证输出

When superpowers:writing-plans completes:

Check structure:

Z02_{feature}_plan.md must exist in ONGOING_DIR (main directive plan)
Z02_CLARIFY_{feature}_plan.md only if NEW questions exist

Report to user:

"Plan created: Z02_{feature}_plan.md"
If clarifications: "Blocking questions in Z02_CLARIFY_{feature}_plan.md"
Next step: "Review clarifications, then use feature-workflow:feature-implementing"

当superpowers:writing-plans完成后：

检查结构：

Z02_{feature}_plan.md必须存在于ONGOING_DIR中（主要指导性计划）
仅当存在新问题时才创建Z02_CLARIFY_{feature}_plan.md

向用户报告：

“计划已创建：Z02_{feature}_plan.md”
如果存在澄清问题：“Z02_CLARIFY_{feature}_plan.md中存在阻塞问题”
下一步：“查看澄清问题，然后使用feature-workflow:feature-implementing”

Red Flags - You're Failing If:

危险信号 - 如果你出现以下情况则表示失败：

Proceeded with unanswered questions in Z01_CLARIFY (BLOCKING - must stop)
Did NOT read CLAUDE.md first (if exists)
CLAUDE.md exists but constraints not passed to planning
Did NOT check for Z01 files*
Directly invoked superpowers:writing-plans without loading Z01 context
Creating plan files with non-standard names (not Z02_{feature}_plan.md)
Saving plans to wrong directory
Used SlashCommand
/superpowers:write-plan
(use Skill tool)
Did NOT explicitly specify output path in prompt to writing-plans
Skipped reading Z01_CLARIFY (if exists)
Using hardcoded paths (detect pattern instead)

在Z01_CLARIFY存在未回答问题的情况下继续（阻塞操作 - 必须停止）
未先阅读CLAUDE.md（如果存在）
CLAUDE.md存在但未将约束传递给计划制定环节
未检查Z01*文件
未加载Z01上下文就直接调用superpowers:writing-plans
使用非标准名称创建计划文件（不是Z02_{feature}_plan.md）
将计划保存到错误的目录
使用SlashCommand
/superpowers:write-plan
（请使用Skill工具）
在给writing-plans的提示中未明确指定输出路径
跳过阅读Z01_CLARIFY（如果存在）
使用硬编码路径（应检测路径模式）

Common Rationalizations

常见合理化借口

Excuse	Reality
"Skip path detection, I know it's docs/ai/ongoing"	NO. Path assumptions break in non-standard repos. Detect ONGOING_DIR.
"No Z01 files, skip check"	NO. Research context critical for quality plans. Check first.
"Superpowers will figure out output structure"	NO. Generic plans lack our research integration. Provide explicit Z02* instruction.
"Read only Z01_research, skip Z01_CLARIFY"	NO. Missing context = incomplete plan. Read ALL Z01* files.
"Create Z02_CLARIFY even if no questions"	NO. Empty files clutter directory. Only create if NEW questions.
"Just invoke superpowers:writing-plans directly"	NO. This wrapper loads Z01 context. That's its value.
"Wrapper skill, no need to track steps"	NO. Wrapper has critical steps (context loading, invocation). Track with TodoWrite.
"TodoWrite adds overhead, skip it"	NO. TodoWrite provides user visibility and prevents skipped steps. MANDATORY.

借口	实际情况
“跳过路径检测，我知道是docs/ai/ongoing”	不行。路径假设在非标准仓库中会失效。必须检测ONGOING_DIR。
“没有Z01文件，跳过检查”	不行。研究上下文对制定高质量计划至关重要。必须先检查。
“Superpowers会自动处理输出结构”	不行。通用计划缺乏我们的研究集成。必须提供明确的Z02*指令。
“只阅读Z01_research，跳过Z01_CLARIFY”	不行。缺少上下文会导致计划不完整。必须阅读所有Z01*文件。
“即使没有问题也创建Z02_CLARIFY”	不行。空文件会使目录杂乱。仅当存在新问题时才创建。
“直接调用superpowers:writing-plans”	不行。此包装器的作用是加载Z01上下文，这是它的价值所在。
“这是包装器Skill，不需要跟踪步骤”	不行。包装器包含关键步骤（上下文加载、调用）。必须使用TodoWrite跟踪。
“TodoWrite增加了工作量，跳过它”	不行。 TodoWrite为用户提供可见性，防止跳过步骤。这是强制要求。

Success Criteria

使用场景

You followed the workflow if:

✓ Read CLAUDE.md if exists
✓ Passed CLAUDE.md constraints to superpowers:writing-plans
✓ Checked for Z01* files
✓ Read ALL Z01* files if they exist
✓ Invoked superpowers:writing-plans skill (NOT slash command)
✓ Explicitly instructed output path in prompt
✓ Verified Z02_{feature}_plan.md was created
✓ Reported next steps to user

工作流位置： 在feature-research（Z01文件）之后，feature-implement之前

在以下情况使用：

Z01研究文件已存在
需要创建实施计划
希望自动化Z01 → Z02工作流

请勿在以下情况使用：

不存在Z01文件 → 先使用feature-research
已有完整的计划
简单的单步任务

When to Use

—

Workflow Position: AFTER feature-research (Z01 files), BEFORE feature-implement

Use when:

Z01 research files exist
Need to create implementation plan
Want automated Z01 → Z02 workflow

Don't use when:

No Z01 files exist → Use feature-research first
Already have complete plan
Simple single-step tasks

—