Files
sar/.agents/skills/bmad-check-implementation-readiness/steps/step-06-final-assessment.md
julian 17c08e6392 chore: initial monorepo scaffold + WDS Phase 1+2 artifacts
- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24)
- apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004)
- apps/web: React 19 + Vite 8 (ESM)
- libs/shared/api-interface: Zod contract base
- Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit
- WDS artifacts:
  - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs)
  - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact)
- Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md
- AGENTS.md + README.md como entrada para devs/agentes

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-27 14:34:20 +00:00

133 lines
3.5 KiB
Markdown

---
outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
---
# Step 6: Final Assessment
## STEP GOAL:
To provide a comprehensive summary of all findings and give the report a final polish, ensuring clear recommendations and overall readiness status.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 📖 You are at the final step - complete the assessment
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- ✅ You are delivering the FINAL ASSESSMENT
- ✅ Your findings are objective and backed by evidence
- ✅ Provide clear, actionable recommendations
- ✅ Success is measured by value of findings
### Step-Specific Rules:
- 🎯 Compile and summarize all findings
- 🚫 Don't soften the message - be direct
- 💬 Provide specific examples for problems
- 🚪 Add final section to the report
## EXECUTION PROTOCOLS:
- 🎯 Review all findings from previous steps
- 💾 Add summary and recommendations
- 📖 Determine overall readiness status
- 🚫 Complete and present final report
## FINAL ASSESSMENT PROCESS:
### 1. Initialize Final Assessment
"Completing **Final Assessment**.
I will now:
1. Review all findings from previous steps
2. Provide a comprehensive summary
3. Add specific recommendations
4. Determine overall readiness status"
### 2. Review Previous Findings
Check the {outputFile} for sections added by previous steps:
- File and FR Validation findings
- UX Alignment issues
- Epic Quality violations
### 3. Add Final Assessment Section
Append to {outputFile}:
```markdown
## Summary and Recommendations
### Overall Readiness Status
[READY/NEEDS WORK/NOT READY]
### Critical Issues Requiring Immediate Action
[List most critical issues that must be addressed]
### Recommended Next Steps
1. [Specific action item 1]
2. [Specific action item 2]
3. [Specific action item 3]
### Final Note
This assessment identified [X] issues across [Y] categories. Address the critical issues before proceeding to implementation. These findings can be used to improve the artifacts or you may choose to proceed as-is.
```
### 4. Complete the Report
- Ensure all findings are clearly documented
- Verify recommendations are actionable
- Add date and assessor information
- Save the final report
### 5. Present Completion
Display:
"**Implementation Readiness Assessment Complete**
Report generated: {outputFile}
The assessment found [number] issues requiring attention. Review the detailed report for specific findings and recommendations."
## WORKFLOW COMPLETE
The implementation readiness workflow is now complete. The report contains all findings and recommendations for the user to consider.
Implementation Readiness complete. Invoke the `bmad-help` skill.
---
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
### ✅ SUCCESS:
- All findings compiled and summarized
- Clear recommendations provided
- Readiness status determined
- Final report saved
### ❌ SYSTEM FAILURE:
- Not reviewing previous findings
- Incomplete summary
- No clear recommendations
## On Complete
Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
If the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.