edit

Author: karaposu

commands/critic-d.md

@@ -69,6 +69,19 @@ Based on context you have of the codebase, task itself and step by step plan; ge
 
  - Make sure generated custom critic is still generic enough but also questions are towards correct and relevant concepts of the feature and the codease, otherwise next phase might miss undocumented details. We want custom critic to be custom tailored to the concepts of the codebase and the feature itself and not to implementation details.    
 
+ - Make sure generated prompt includes output instructions "Create a `critic.md` file in the same directory as the implementation plan. And this output file has high level summary on top". 
+
+ - Make sure generated prompt includes:
+
+ """
+## Output Format
+
+For each risk found, document:
+
+Desc, Risk Desc, Severity (| Low / Medium / High |), Impact, ELI5 desc, Affected areas,  Mitigation** (Medium/High only) and Category (| Breaking change / Import error / Circular import / Package discovery / Stale cache / Missing file / Phase ordering |)
+
+ """
+
   - Save the generated prompt** as `dynamic_critic_prompt.md` in the same directory as the `step_by_step_plan.md`.
  - Print the generated prompt** in the conversation so the user can read it.
  - Ask the user: *"Here's the dynamic critic prompt I generated. Should I run it now?"*

commands/dead-code-index.md

@@ -32,6 +32,7 @@ For each candidate, document:
 - **Assumed intent** — based on the code's content (naming, structure, fields, parameters), what was this likely meant to do? What direction was it heading? This is inference, not fact — label it as such.
 - **Confidence** (Definite / Likely / Uncertain)
 - **Search command** — a ready-to-run `grep -rn` command to find all mentions of this code in the codebase
+- **Mark for removal in future?** — (leave empty — human marks "yes" to approve future removal)
 
 Do NOT delete anything. This is an inventory only.
 

src/APPENDIX4_Adding_New_Feature.md

@@ -83,7 +83,7 @@ Suggest mitigation strategies for Medium/High risks.
 Analyze how this feature will interact with the existing codebase:
 
 1. Read all relevant module interfaces and implementations
-2. Create devdocs/features/planned/feat_X_[FEATURE_NAME]/critic.md
+2. Create critic.md in step by step plan directory
 
 
 

src/APPENDIX5_Useful.md

@@ -148,6 +148,7 @@ For each candidate, document:
 - **Assumed intent** — based on the code's content (naming, structure, fields, parameters), what was this likely meant to do? What direction was it heading? This is inference, not fact — label it as such.
 - **Confidence** (Definite / Likely / Uncertain)
 - **Search command** — a ready-to-run `grep -rn` command to find all mentions of this code in the codebase
+- **Mark for removal in future?** — (empty — human marks "yes" to approve future removal)
 
 Do NOT delete anything. This is an inventory only.