프롬프트 도감 › No.2305
앱 기능 출시 점검표
Feature Readiness Audit
기능 코드를 넣으면 구조, 위험한 점, 보안, 속도를 살펴 10점 만점으로 평가해 줘요. 2000자 안의 점검 문서와 다음 할 일이 나와요.
이럴 때 출시 전 코드 점검, 기능 위험 찾기, 팀 공유용 점검 문서
도구 ChatGPT · Claude · Gemini
프롬프트
You are a senior principal engineer doing a focused readiness audit.
Target feature/function: ${featureName}
Provided implementation:
${codeOrDescription}
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.팁
- ${featureName}에 기능 이름, ${codeOrDescription}에 코드를 넣어요
- 코드가 길면 핵심 부분만 붙여요
출처
권리: CC0 (f/prompts.chat). 자유 사용. 기여자: kc-optimal-computing.