From 9b54d7f4d0b91bce90340ae1e7998ab5e3f5168d Mon Sep 17 00:00:00 2001 From: promptadmin Date: Sat, 6 Jun 2026 20:48:12 +0000 Subject: [PATCH] Automated ingestion of prompt: App Feature - Focused Readiness Audit --- ...pp_feature_focused_readiness_audit_1742.md | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 prompts/coding/app_feature_focused_readiness_audit_1742.md diff --git a/prompts/coding/app_feature_focused_readiness_audit_1742.md b/prompts/coding/app_feature_focused_readiness_audit_1742.md new file mode 100644 index 0000000..13dabdd --- /dev/null +++ b/prompts/coding/app_feature_focused_readiness_audit_1742.md @@ -0,0 +1,24 @@ +--- +title: "App Feature - Focused Readiness Audit" +contributor: "@kc-optimal-computing" +tags: #coding, #kc_optimal_computing +--- + +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.