@zeyue0329/xiaoma-cli 1.0.49 → 6.0.0-alpha.13

package/xiaoma-core/checklists/qa-approval-checklist.md

@@ -1,393 +0,0 @@
-# QA测试验收检查清单
-
-## 检查清单概述
-
-本检查清单用于QA团队对开发完成的用户故事进行全面的测试验证，确保功能质量、性能表现和用户体验都达到发布标准。
-
-## 功能测试验证
-
-### 验收标准验证
-
-- [ ] **标准1验证**: 第一个验收标准完全满足
-- [ ] **标准2验证**: 第二个验收标准完全满足
-- [ ] **标准3验证**: 第三个验收标准完全满足
-- [ ] **标准N验证**: 所有验收标准逐一验证通过
-- [ ] **交叉验证**: 验收标准之间的交互验证
-
-### 核心功能测试
-
-- [ ] **主要流程**: 核心业务流程功能正常
-- [ ] **数据创建**: 数据创建功能正确工作
-- [ ] **数据查询**: 数据查询功能返回正确结果
-- [ ] **数据更新**: 数据更新功能正确处理
-- [ ] **数据删除**: 数据删除功能安全有效
-
-### 用户界面测试 (如适用)
-
-- [ ] **界面布局**: 页面布局正确美观
-- [ ] **交互响应**: 用户交互响应及时
-- [ ] **数据显示**: 数据显示格式正确
-- [ ] **错误提示**: 错误提示信息用户友好
-- [ ] **表单验证**: 表单验证逻辑正确
-
-### 业务流程测试
-
-- [ ] **完整流程**: 端到端业务流程测试
-- [ ] **分支流程**: 各种业务分支流程测试
-- [ ] **状态转换**: 数据状态转换正确
-- [ ] **权限控制**: 权限和角色控制有效
-- [ ] **审计跟踪**: 操作审计记录完整
-
-## API接口测试
-
-### API契约测试
-
-- [ ] **请求格式**: 请求参数格式符合API规范
-- [ ] **响应格式**: 响应数据格式符合API规范
-- [ ] **HTTP状态码**: 状态码使用正确
-- [ ] **请求头**: 请求头处理正确
-- [ ] **响应头**: 响应头信息完整
-
-### API功能测试
-
-- [ ] **GET接口**: 查询接口功能正常
-- [ ] **POST接口**: 创建接口功能正常
-- [ ] **PUT接口**: 更新接口功能正常
-- [ ] **DELETE接口**: 删除接口功能正常
-- [ ] **分页接口**: 分页查询功能正常
-
-### API参数测试
-
-- [ ] **必填参数**: 必填参数验证生效
-- [ ] **可选参数**: 可选参数处理正确
-- [ ] **参数类型**: 参数类型验证正确
-- [ ] **参数范围**: 参数值范围验证有效
-- [ ] **参数组合**: 参数组合逻辑正确
-
-### API错误处理
-
-- [ ] **400错误**: 客户端请求错误处理正确
-- [ ] **401错误**: 认证失败错误处理正确
-- [ ] **403错误**: 权限不足错误处理正确
-- [ ] **404错误**: 资源不存在错误处理正确
-- [ ] **500错误**: 服务器错误处理graceful
-
-## 数据库测试验证
-
-### 数据完整性测试
-
-- [ ] **主键约束**: 主键唯一性约束生效
-- [ ] **外键约束**: 外键关联关系正确
-- [ ] **唯一约束**: 唯一性约束生效
-- [ ] **非空约束**: 非空字段约束生效
-- [ ] **检查约束**: 检查约束验证有效
-
-### 数据操作测试
-
-- [ ] **插入操作**: 数据插入操作正确
-- [ ] **查询操作**: 数据查询结果准确
-- [ ] **更新操作**: 数据更新操作安全
-- [ ] **删除操作**: 数据删除操作正确
-- [ ] **批量操作**: 批量数据操作有效
-
-### 数据一致性测试
-
-- [ ] **事务一致性**: 事务操作保持数据一致性
-- [ ] **并发一致性**: 并发操作数据一致性
-- [ ] **关联一致性**: 关联数据一致性维护
-- [ ] **状态一致性**: 数据状态转换一致性
-- [ ] **审计一致性**: 审计字段维护一致性
-
-### 数据安全测试
-
-- [ ] **软删除**: 删除操作使用软删除
-- [ ] **数据权限**: 数据访问权限控制
-- [ ] **敏感数据**: 敏感数据处理安全
-- [ ] **数据备份**: 数据变更可追溯
-- [ ] **数据恢复**: 错误操作可恢复
-
-## 边界条件和异常测试
-
-### 边界值测试
-
-- [ ] **最小值**: 最小边界值测试
-- [ ] **最大值**: 最大边界值测试
-- [ ] **临界值**: 临界边界值测试
-- [ ] **空值处理**: 空值和null值处理
-- [ ] **特殊字符**: 特殊字符处理测试
-
-### 异常情况测试
-
-- [ ] **网络异常**: 网络超时和断线处理
-- [ ] **数据库异常**: 数据库连接异常处理
-- [ ] **系统异常**: 系统级异常处理
-- [ ] **业务异常**: 业务逻辑异常处理
-- [ ] **资源异常**: 资源不足异常处理
-
-### 错误恢复测试
-
-- [ ] **错误重试**: 错误后自动重试机制
-- [ ] **数据回滚**: 错误操作数据回滚
-- [ ] **状态恢复**: 异常后状态恢复
-- [ ] **用户通知**: 错误信息用户通知
-- [ ] **系统恢复**: 系统故障后恢复能力
-
-## 性能测试验证
-
-### 响应时间测试
-
-- [ ] **API响应时间**: API接口响应时间 < 500ms
-- [ ] **页面加载时间**: 页面加载时间 < 2s (如适用)
-- [ ] **数据库查询时间**: 数据库查询时间 < 200ms
-- [ ] **批量操作时间**: 批量操作响应时间合理
-- [ ] **复杂查询时间**: 复杂查询响应时间可接受
-
-### 并发性能测试
-
-- [ ] **并发用户**: 支持预期并发用户数
-- [ ] **并发请求**: 并发请求处理正常
-- [ ] **资源竞争**: 资源竞争处理正确
-- [ ] **死锁避免**: 无死锁情况发生
-- [ ] **性能衰减**: 并发增加性能衰减可接受
-
-### 资源使用测试
-
-- [ ] **CPU使用率**: CPU使用率在正常范围
-- [ ] **内存使用**: 内存使用合理无泄漏
-- [ ] **数据库连接**: 数据库连接池使用正常
-- [ ] **磁盘空间**: 磁盘空间使用合理
-- [ ] **网络带宽**: 网络带宽使用效率高
-
-## 安全性测试
-
-### 认证和授权测试
-
-- [ ] **身份认证**: 用户身份认证机制有效
-- [ ] **访问控制**: 资源访问控制正确
-- [ ] **权限验证**: 操作权限验证生效
-- [ ] **会话管理**: 用户会话管理安全
-- [ ] **令牌验证**: API令牌验证有效
-
-### 输入安全测试
-
-- [ ] **SQL注入**: SQL注入攻击防护
-- [ ] **XSS攻击**: 跨站脚本攻击防护
-- [ ] **CSRF攻击**: 跨站请求伪造防护
-- [ ] **输入验证**: 输入数据验证充分
-- [ ] **文件上传**: 文件上传安全验证
-
-### 数据安全测试
-
-- [ ] **敏感数据**: 敏感数据加密存储
-- [ ] **数据传输**: 数据传输加密保护
-- [ ] **日志安全**: 日志中无敏感信息
-- [ ] **错误信息**: 错误信息不泄露敏感内容
-- [ ] **数据脱敏**: 查询结果适当脱敏
-
-## 兼容性测试
-
-### 浏览器兼容性 (如适用)
-
-- [ ] **Chrome**: Chrome浏览器兼容性
-- [ ] **Firefox**: Firefox浏览器兼容性
-- [ ] **Safari**: Safari浏览器兼容性
-- [ ] **Edge**: Edge浏览器兼容性
-- [ ] **移动端**: 移动端浏览器兼容性
-
-### 系统兼容性
-
-- [ ] **操作系统**: 不同操作系统兼容性
-- [ ] **Java版本**: Java版本兼容性
-- [ ] **数据库版本**: 数据库版本兼容性
-- [ ] **中间件版本**: 中间件版本兼容性
-- [ ] **第三方依赖**: 第三方库版本兼容性
-
-### API版本兼容性
-
-- [ ] **向后兼容**: API向后兼容性
-- [ ] **版本控制**: API版本控制机制
-- [ ] **迁移支持**: 版本迁移支持
-- [ ] **废弃通知**: 废弃功能通知机制
-- [ ] **文档一致**: 版本文档一致性
-
-## 可用性测试
-
-### 用户体验测试
-
-- [ ] **操作流畅性**: 用户操作流畅自然
-- [ ] **界面友好性**: 界面设计用户友好
-- [ ] **错误提示**: 错误提示信息明确
-- [ ] **帮助信息**: 帮助和说明信息充分
-- [ ] **反馈机制**: 操作反馈及时明确
-
-### 可访问性测试
-
-- [ ] **键盘导航**: 支持键盘导航
-- [ ] **屏幕阅读器**: 支持屏幕阅读器
-- [ ] **色彩对比**: 色彩对比度充分
-- [ ] **字体大小**: 字体大小适当可调
-- [ ] **多语言**: 多语言支持完整
-
-## 回归测试
-
-### 相关功能测试
-
-- [ ] **直接相关**: 直接相关功能无回归
-- [ ] **间接相关**: 间接相关功能无影响
-- [ ] **共享组件**: 共享组件功能正常
-- [ ] **数据依赖**: 数据依赖功能无影响
-- [ ] **API依赖**: API依赖功能无问题
-
-### 系统级回归测试
-
-- [ ] **核心流程**: 系统核心流程无回归
-- [ ] **集成点**: 系统集成点功能正常
-- [ ] **性能指标**: 系统性能指标无退化
-- [ ] **安全特性**: 系统安全特性无影响
-- [ ] **配置管理**: 系统配置管理正常
-
-## 测试环境验证
-
-### 环境配置检查
-
-- [ ] **数据库环境**: 测试数据库环境正确
-- [ ] **应用配置**: 应用配置参数正确
-- [ ] **网络环境**: 网络连接和配置正常
-- [ ] **第三方服务**: 第三方服务连接正常
-- [ ] **日志配置**: 日志配置和输出正常
-
-### 测试数据准备
-
-- [ ] **基础数据**: 基础测试数据完整
-- [ ] **边界数据**: 边界测试数据准备
-- [ ] **异常数据**: 异常测试数据准备
-- [ ] **性能数据**: 性能测试数据准备
-- [ ] **数据清理**: 测试后数据清理机制
-
-## 测试结果记录
-
-### 测试执行记录
-
-- [ ] **测试用例**: 执行的测试用例记录
-- [ ] **测试步骤**: 详细的测试步骤记录
-- [ ] **测试数据**: 使用的测试数据记录
-- [ ] **执行结果**: 每个测试的执行结果
-- [ ] **缺陷记录**: 发现的缺陷详细记录
-
-### 问题分析记录
-
-- [ ] **问题描述**: 详细的问题描述
-- [ ] **重现步骤**: 问题重现的具体步骤
-- [ ] **影响评估**: 问题影响范围和严重程度
-- [ ] **根因分析**: 问题根本原因分析
-- [ ] **修复建议**: 问题修复建议
-
-### 测试报告生成
-
-- [ ] **测试摘要**: 测试执行情况摘要
-- [ ] **通过率**: 测试用例通过率统计
-- [ ] **缺陷统计**: 缺陷数量和分布统计
-- [ ] **风险评估**: 质量风险评估
-- [ ] **发布建议**: 发布准备就绪建议
-
-## 质量评估标准
-
-### 功能质量标准
-
-- [ ] **功能完整性**: 所有功能需求都已实现 ≥ 100%
-- [ ] **验收标准**: 所有验收标准都通过 = 100%
-- [ ] **缺陷密度**: 严重缺陷数量 = 0
-- [ ] **功能正确性**: 功能正确性 ≥ 99%
-- [ ] **业务逻辑**: 业务逻辑正确性 = 100%
-
-### 性能质量标准
-
-- [ ] **响应时间**: API响应时间 < 500ms
-- [ ] **并发能力**: 支持并发用户数达标
-- [ ] **资源使用**: 资源使用效率 ≥ 80%
-- [ ] **性能稳定性**: 性能表现稳定一致
-- [ ] **扩展性**: 具备良好的扩展性
-
-### 安全质量标准
-
-- [ ] **安全漏洞**: 高危安全漏洞数量 = 0
-- [ ] **认证机制**: 认证机制100%有效
-- [ ] **授权控制**: 授权控制100%正确
-- [ ] **数据保护**: 敏感数据100%保护
-- [ ] **输入验证**: 输入验证100%有效
-
-## 验收决策
-
-### 通过标准 (所有项目必须满足)
-
-- [ ] **所有验收标准通过**: ✅
-- [ ] **功能测试全部通过**: ✅
-- [ ] **API测试全部通过**: ✅
-- [ ] **性能测试达到要求**: ✅
-- [ ] **安全测试无高危问题**: ✅
-- [ ] **回归测试无问题**: ✅
-- [ ] **无阻塞性缺陷**: ✅
-
-### 验收通过操作
-
-如果所有测试都通过：
-
-- [ ] 更新故事状态: `Review → Done`
-- [ ] 记录测试完成时间: `{当前时间}`
-- [ ] 生成QA测试报告
-- [ ] 通知相关团队成员
-- [ ] 标记功能可以发布
-
-### 验收失败处理
-
-如果测试发现问题：
-
-- [ ] 详细记录所有问题
-- [ ] 评估问题严重程度和影响范围
-- [ ] 创建缺陷报告分配给开发团队
-- [ ] 更新故事状态: `Review → InProgress`
-- [ ] 等待开发修复后重新测试
-
-## 持续改进
-
-### 测试过程改进
-
-- [ ] **测试效率**: 记录测试执行效率数据
-- [ ] **问题模式**: 分析常见问题模式
-- [ ] **测试覆盖**: 评估测试覆盖充分性
-- [ ] **自动化机会**: 识别自动化测试机会
-- [ ] **流程优化**: 提出流程优化建议
-
-### 质量度量
-
-- [ ] **缺陷趋势**: 跟踪缺陷数量和趋势
-- [ ] **修复效率**: 统计问题修复效率
-- [ ] **测试周期**: 记录测试周期时间
-- [ ] **客户满意度**: 收集用户反馈
-- [ ] **团队协作**: 评估团队协作效果
-
-## 使用说明
-
-### 测试流程
-
-1. 接收开发完成的用户故事(Review状态)
-2. 准备测试环境和测试数据
-3. 按照检查清单逐项执行测试
-4. 记录测试结果和发现的问题
-5. 根据测试结果做出验收决策
-
-### 测试技巧
-
-- 从最终用户角度进行功能测试
-- 重点关注验收标准的验证
-- 注意边界条件和异常情况
-- 考虑与其他功能的集成影响
-- 关注性能和安全性要求
-
-### 常见问题处理
-
-- **API文档不一致**: 要求更新API文档
-- **性能不达标**: 要求优化性能
-- **错误处理不当**: 要求改进错误处理
-- **安全漏洞**: 要求修复安全问题
-- **用户体验问题**: 要求改进交互设计

package/xiaoma-core/checklists/story-dod-checklist.md

@@ -1,96 +0,0 @@
-<!-- Powered by XiaoMa™ Core -->
-
-# Story Definition of Done (DoD) Checklist
-
-## Instructions for Developer Agent
-
-Before marking a story as 'Review', please go through each item in this checklist. Report the status of each item (e.g., [x] Done, [ ] Not Done, [N/A] Not Applicable) and provide brief comments if necessary.
-
-[[LLM: INITIALIZATION INSTRUCTIONS - STORY DOD VALIDATION
-
-This checklist is for DEVELOPER AGENTS to self-validate their work before marking a story complete.
-
-IMPORTANT: This is a self-assessment. Be honest about what's actually done vs what should be done. It's better to identify issues now than have them found in review.
-
-EXECUTION APPROACH:
-
-1. Go through each section systematically
-2. Mark items as [x] Done, [ ] Not Done, or [N/A] Not Applicable
-3. Add brief comments explaining any [ ] or [N/A] items
-4. Be specific about what was actually implemented
-5. Flag any concerns or technical debt created
-
-The goal is quality delivery, not just checking boxes.]]
-
-## Checklist Items
-
-1. **Requirements Met:**
-
-   [[LLM: Be specific - list each requirement and whether it's complete]]
-   - [ ] All functional requirements specified in the story are implemented.
-   - [ ] All acceptance criteria defined in the story are met.
-
-2. **Coding Standards & Project Structure:**
-
-   [[LLM: Code quality matters for maintainability. Check each item carefully]]
-   - [ ] All new/modified code strictly adheres to `Operational Guidelines`.
-   - [ ] All new/modified code aligns with `Project Structure` (file locations, naming, etc.).
-   - [ ] Adherence to `Tech Stack` for technologies/versions used (if story introduces or modifies tech usage).
-   - [ ] Adherence to `Api Reference` and `Data Models` (if story involves API or data model changes).
-   - [ ] Basic security best practices (e.g., input validation, proper error handling, no hardcoded secrets) applied for new/modified code.
-   - [ ] No new linter errors or warnings introduced.
-   - [ ] Code is well-commented where necessary (clarifying complex logic, not obvious statements).
-
-3. **Testing:**
-
-   [[LLM: Testing proves your code works. Be honest about test coverage]]
-   - [ ] All required unit tests as per the story and `Operational Guidelines` Testing Strategy are implemented.
-   - [ ] All required integration tests (if applicable) as per the story and `Operational Guidelines` Testing Strategy are implemented.
-   - [ ] All tests (unit, integration, E2E if applicable) pass successfully.
-   - [ ] Test coverage meets project standards (if defined).
-
-4. **Functionality & Verification:**
-
-   [[LLM: Did you actually run and test your code? Be specific about what you tested]]
-   - [ ] Functionality has been manually verified by the developer (e.g., running the app locally, checking UI, testing API endpoints).
-   - [ ] Edge cases and potential error conditions considered and handled gracefully.
-
-5. **Story Administration:**
-
-   [[LLM: Documentation helps the next developer. What should they know?]]
-   - [ ] All tasks within the story file are marked as complete.
-   - [ ] Any clarifications or decisions made during development are documented in the story file or linked appropriately.
-   - [ ] The story wrap up section has been completed with notes of changes or information relevant to the next story or overall project, the agent model that was primarily used during development, and the changelog of any changes is properly updated.
-
-6. **Dependencies, Build & Configuration:**
-
-   [[LLM: Build issues block everyone. Ensure everything compiles and runs cleanly]]
-   - [ ] Project builds successfully without errors.
-   - [ ] Project linting passes
-   - [ ] Any new dependencies added were either pre-approved in the story requirements OR explicitly approved by the user during development (approval documented in story file).
-   - [ ] If new dependencies were added, they are recorded in the appropriate project files (e.g., `package.json`, `requirements.txt`) with justification.
-   - [ ] No known security vulnerabilities introduced by newly added and approved dependencies.
-   - [ ] If new environment variables or configurations were introduced by the story, they are documented and handled securely.
-
-7. **Documentation (If Applicable):**
-
-   [[LLM: Good documentation prevents future confusion. What needs explaining?]]
-   - [ ] Relevant inline code documentation (e.g., JSDoc, TSDoc, Python docstrings) for new public APIs or complex logic is complete.
-   - [ ] User-facing documentation updated, if changes impact users.
-   - [ ] Technical documentation (e.g., READMEs, system diagrams) updated if significant architectural changes were made.
-
-## Final Confirmation
-
-[[LLM: FINAL DOD SUMMARY
-
-After completing the checklist:
-
-1. Summarize what was accomplished in this story
-2. List any items marked as [ ] Not Done with explanations
-3. Identify any technical debt or follow-up work needed
-4. Note any challenges or learnings for future stories
-5. Confirm whether the story is truly ready for review
-
-Be honest - it's better to flag issues now than have them discovered later.]]
-
-- [ ] I, the Developer Agent, confirm that all applicable items above have been addressed.

package/xiaoma-core/checklists/story-draft-checklist.md

@@ -1,155 +0,0 @@
-<!-- Powered by XiaoMa™ Core -->
-
-# Story Draft Checklist
-
-The Scrum Master should use this checklist to validate that each story contains sufficient context for a developer agent to implement it successfully, while assuming the dev agent has reasonable capabilities to figure things out.
-
-[[LLM: INITIALIZATION INSTRUCTIONS - STORY DRAFT VALIDATION
-
-Before proceeding with this checklist, ensure you have access to:
-
-1. The story document being validated (usually in docs/stories/ or provided directly)
-2. The parent epic context
-3. Any referenced architecture or design documents
-4. Previous related stories if this builds on prior work
-
-IMPORTANT: This checklist validates individual stories BEFORE implementation begins.
-
-VALIDATION PRINCIPLES:
-
-1. Clarity - A developer should understand WHAT to build
-2. Context - WHY this is being built and how it fits
-3. Guidance - Key technical decisions and patterns to follow
-4. Testability - How to verify the implementation works
-5. Self-Contained - Most info needed is in the story itself
-
-REMEMBER: We assume competent developer agents who can:
-
-- Research documentation and codebases
-- Make reasonable technical decisions
-- Follow established patterns
-- Ask for clarification when truly stuck
-
-We're checking for SUFFICIENT guidance, not exhaustive detail.]]
-
-## 1. GOAL & CONTEXT CLARITY
-
-[[LLM: Without clear goals, developers build the wrong thing. Verify:
-
-1. The story states WHAT functionality to implement
-2. The business value or user benefit is clear
-3. How this fits into the larger epic/product is explained
-4. Dependencies are explicit ("requires Story X to be complete")
-5. Success looks like something specific, not vague]]
-
-- [ ] Story goal/purpose is clearly stated
-- [ ] Relationship to epic goals is evident
-- [ ] How the story fits into overall system flow is explained
-- [ ] Dependencies on previous stories are identified (if applicable)
-- [ ] Business context and value are clear
-
-## 2. TECHNICAL IMPLEMENTATION GUIDANCE
-
-[[LLM: Developers need enough technical context to start coding. Check:
-
-1. Key files/components to create or modify are mentioned
-2. Technology choices are specified where non-obvious
-3. Integration points with existing code are identified
-4. Data models or API contracts are defined or referenced
-5. Non-standard patterns or exceptions are called out
-
-Note: We don't need every file listed - just the important ones.]]
-
-- [ ] Key files to create/modify are identified (not necessarily exhaustive)
-- [ ] Technologies specifically needed for this story are mentioned
-- [ ] Critical APIs or interfaces are sufficiently described
-- [ ] Necessary data models or structures are referenced
-- [ ] Required environment variables are listed (if applicable)
-- [ ] Any exceptions to standard coding patterns are noted
-
-## 3. REFERENCE EFFECTIVENESS
-
-[[LLM: References should help, not create a treasure hunt. Ensure:
-
-1. References point to specific sections, not whole documents
-2. The relevance of each reference is explained
-3. Critical information is summarized in the story
-4. References are accessible (not broken links)
-5. Previous story context is summarized if needed]]
-
-- [ ] References to external documents point to specific relevant sections
-- [ ] Critical information from previous stories is summarized (not just referenced)
-- [ ] Context is provided for why references are relevant
-- [ ] References use consistent format (e.g., `docs/filename.md#section`)
-
-## 4. SELF-CONTAINMENT ASSESSMENT
-
-[[LLM: Stories should be mostly self-contained to avoid context switching. Verify:
-
-1. Core requirements are in the story, not just in references
-2. Domain terms are explained or obvious from context
-3. Assumptions are stated explicitly
-4. Edge cases are mentioned (even if deferred)
-5. The story could be understood without reading 10 other documents]]
-
-- [ ] Core information needed is included (not overly reliant on external docs)
-- [ ] Implicit assumptions are made explicit
-- [ ] Domain-specific terms or concepts are explained
-- [ ] Edge cases or error scenarios are addressed
-
-## 5. TESTING GUIDANCE
-
-[[LLM: Testing ensures the implementation actually works. Check:
-
-1. Test approach is specified (unit, integration, e2e)
-2. Key test scenarios are listed
-3. Success criteria are measurable
-4. Special test considerations are noted
-5. Acceptance criteria in the story are testable]]
-
-- [ ] Required testing approach is outlined
-- [ ] Key test scenarios are identified
-- [ ] Success criteria are defined
-- [ ] Special testing considerations are noted (if applicable)
-
-## VALIDATION RESULT
-
-[[LLM: FINAL STORY VALIDATION REPORT
-
-Generate a concise validation report:
-
-1. Quick Summary
-   - Story readiness: READY / NEEDS REVISION / BLOCKED
-   - Clarity score (1-10)
-   - Major gaps identified
-
-2. Fill in the validation table with:
-   - PASS: Requirements clearly met
-   - PARTIAL: Some gaps but workable
-   - FAIL: Critical information missing
-
-3. Specific Issues (if any)
-   - List concrete problems to fix
-   - Suggest specific improvements
-   - Identify any blocking dependencies
-
-4. Developer Perspective
-   - Could YOU implement this story as written?
-   - What questions would you have?
-   - What might cause delays or rework?
-
-Be pragmatic - perfect documentation doesn't exist, but it must be enough to provide the extreme context a dev agent needs to get the work down and not create a mess.]]
-
-| Category                             | Status | Issues |
-| ------------------------------------ | ------ | ------ |
-| 1. Goal & Context Clarity            | _TBD_  |        |
-| 2. Technical Implementation Guidance | _TBD_  |        |
-| 3. Reference Effectiveness           | _TBD_  |        |
-| 4. Self-Containment Assessment       | _TBD_  |        |
-| 5. Testing Guidance                  | _TBD_  |        |
-
-**Final Assessment:**
-
-- READY: The story provides sufficient context for implementation
-- NEEDS REVISION: The story requires updates (see issues)
-- BLOCKED: External information required (specify what information)

package/xiaoma-core/core-config.yaml

@@ -1,23 +0,0 @@
-# <!-- Powered by XiaoMa™ Core -->
-markdownExploder: true
-qa:
-  qaLocation: docs/qa
-prd:
-  prdFile: docs/prd.md
-  prdVersion: v4
-  prdSharded: true
-  prdShardedLocation: docs/prd
-  epicFilePattern: epic-{n}*.md
-architecture:
-  architectureFile: docs/architecture.md
-  architectureVersion: v4
-  architectureSharded: true
-  architectureShardedLocation: docs/architecture
-customTechnicalDocuments: null
-devLoadAlwaysFiles:
-  - docs/architecture/coding-standards.md
-  - docs/architecture/tech-stack.md
-  - docs/architecture/source-tree.md
-devDebugLog: .ai/debug-log.md
-devStoryLocation: docs/stories
-slashPrefix: XiaoMa