Source original Skill
- Source: superpowers delivery wrap-up capability (migrated to aile-only)
- Strategy: retain the wrap-up decision and delivery description structure, and strengthen the team PR/Jira contract.
Overview
This skill is used when submitting a PR, with the goal of letting CR/QA/PM complete acceptance in one entry point:
- The PR must cite the plan and design artifacts
- The PR must declare verification items (tests/build, etc.) - (Optional) automatically write the PR link back to Jira and transition the status
Workflow Overview
项目初始化:project-docs-init(创建文档)
↓
需求分析:aile-requirement-analysis(结构化需求分析 + 更新文档)
↓
计划制定:aile-writing-plans(设计 + 计划)
↓
执行开发:aile-executing-plans 或 aile-subagent-dev(按计划执行 + 人工检查点)
↓
交付总结:aile-delivery-report(整理交付材料 + 回链 Story)
Output Contract
The PR Description must use the template:docs-templates/stage3-pr-description-template.md。
Must include at least:
- Jira Story Key + link
- Plan Reference:
docs/plans/{Story-Key}/analysis.md(and optionaldesign.pencil) - Change Summary (2-3 sentences)
- Verification (checklist items)
Execution Flow
- From
analysis.mdextract the Story-Key and plan references - Generate the PR Description according to the template (can be pasted directly into the PR platform)
3. (Optional) If Jira MCP is enabled:
- Paste the PR link in the Story Comment and @mention the development owner
- When the Jira status changes, call
jira_update_issueto update the corresponding Story's status field to developed