返回 Skill 列表
extension
分类: 开发与工程无需 API Key

aico-pm-story-acceptance

在前端/后端任务完成后验证并关闭故事。检查所有相关的任务文件,更新故事验收标准复选框。独特价值:确保在关闭故事之前同时验证前端和后端的任务。防止过早关闭故事。使用此技能的情况包括:- 前端或后端通知“任务已完成,请验证”- 用户请求“验证故事”,“接受故事”,“关闭故事”,“标记故事为完成”- 需要检查某个故事是否可以被标记为完成- 用户询问“故事X完成了吗?”、“我们可以关闭故事X了吗?”关键点:在关闭之前必须同时检查前端任务(docs/reference/frontend/tasks/)和后端任务(docs/reference/backend/tasks/)。输出:将故事文件中的复选框从`- [ ]`更新为`- [x]`。

person作者: jakexiaohubgithub

Story Acceptance

Language Configuration

Before generating any content, check aico.json in project root for language field to determine the output language. If not set, default to English.

Process

  1. Identify the story: Get story ID (e.g., S-001) from notification or user
  2. Read the story: Load docs/reference/pm/stories/{story-id}.md
  3. Find related tasks (use Strategy 1 if available, fallback to Strategy 2):
    • Strategy 1 (Preferred): Read "Related Tasks" section from story file
      • Story file should contain task list created by task-breakdown
      • Directly read the listed task files
    • Strategy 2 (Fallback): Pattern matching in task directories
      • Extract story name from story filename (e.g., "user-profile" from "user-profile.md")
      • Search docs/reference/frontend/tasks/ for story-{story-name}-*.md
      • Search docs/reference/backend/tasks/ for story-{story-name}-*.md
  4. Verify all tasks completed:
    • Read each task file's > **Status**: field
    • All task statuses should be completed
    • No pending or in_progress tasks remaining
  5. Update story:
    • If ALL tasks completed → Update acceptance criteria - [ ] to - [x]
    • If partial → Report progress, list incomplete tasks

Verification Checklist

## Story: S-XXX

### Frontend Tasks

- [x] docs/reference/frontend/tasks/s-xxx.md - All completed

### Backend Tasks

- [x] docs/reference/backend/tasks/s-xxx.md - All completed

### Result: ✅ Ready to close / ⏳ Waiting for tasks

Task Status Mapping

| Task Status | Meaning | | ---------------- | ----------------- | | ✅ completed | Task done | | 🔄 in_progress | Currently working | | ⏳ pending | Not started |

Story Update Format

When all tasks are complete, update the story file:

## Acceptance Criteria

- [x] Criterion 1 (was `- [ ]`)
- [x] Criterion 2 (was `- [ ]`)
- [x] Criterion 3 (was `- [ ]`)

Decision Logic

Has frontend tasks? ──Yes──> Check frontend/tasks/{story}.md
        │                            │
        No                     All completed?
        │                       │        │
        ▼                      Yes       No
Has backend tasks? ──Yes──> Check backend/tasks/{story}.md
        │                            │
        No                     All completed?
        │                       │        │
        ▼                      Yes       No
All checks passed? ─────────────┘        │
        │                                │
       Yes                              No
        │                                │
        ▼                                ▼
Update story checkboxes          Report incomplete tasks

Key Rules

  • MUST check BOTH frontend and backend tasks before closing
  • ONLY update story when ALL related tasks are completed
  • ALWAYS report which tasks are still pending if not ready to close
  • Use exact checkbox format: - [x] for completed, - [ ] for pending

Output Examples

All Complete

## Story S-001 Acceptance Result

✅ **Ready to Close**

### Task Check
- Frontend: 3/3 completed
- Backend: 2/2 completed

Story acceptance criteria updated.

Partial Complete

## Story S-001 Acceptance Result

⏳ **Waiting for Tasks**

### Task Check
- Frontend: 3/3 completed ✅
- Backend: 1/2 completed ⏳

### Incomplete Tasks
- [ ] Backend Task 2: Implement API endpoint

Common Mistakes

  • ❌ Close story with pending tasks → ✅ Check ALL related tasks first
  • ❌ Only check frontend OR backend → ✅ Check BOTH if story has both
  • ❌ Forget to update checkboxes → ✅ Always update - [ ] to - [x]