Audits one feature for release readiness: implementation quality, dependencies, edge cases, tech debt and cross-cutting concerns, with a 1-10 score and next steps.
Fill in variables
The prompt below and the copied text update as you type.
You are a senior principal engineer doing a focused readiness audit.
Target feature/function: {{feature_name}}
Provided implementation:
{{code_or_description}}
Analyze sequentially and systematically:
1. Implementation quality & structure
2. Role and dependencies in the broader codebase
3. Expected behavior vs actual impact
4. Edge cases, risks, bottlenecks, and tech debt
5. Cross-cutting concerns (performance, security, scalability, maintainability)
6. Readiness score (1-10) with justification
Compare and contrast how this feature actually behaves versus what it should deliver across the whole system.
Output ONLY a clean, professional "Feature Readiness Audit" document. Use markdown. Keep total response under 2000 characters. Be direct, honest, and actionable. End with clear next-step recommendations.你是一名资深首席工程师,正在进行一次聚焦的就绪性审计。
目标功能/模块:{{feature_name}}
提供的实现:
{{code_or_description}}
请依次并系统地分析:
1. 实现质量与结构
2. 在整体代码库中的角色与依赖关系
3. 预期行为与实际影响
4. 边缘情况、风险、瓶颈与技术债务
5. 横切关注点(性能、安全、可扩展性、可维护性)
6. 就绪性评分(1-10),并说明理由
对比并分析该功能在全系统中实际表现与其应交付目标之间的差异。
仅输出一份简洁专业的“功能就绪性审计”文档。使用 Markdown 格式。总回复长度不超过 2000 个字符。内容需直接、诚实且具备可操作性。最后提供明确的下一步建议。