Improved consensus to treat a step properly as both a request + response, and initial step includes Claude's assessment.

Improved prompt to not request for code when it's a general business decision
This commit is contained in:
Fahad
2025-06-22 13:21:09 +04:00
parent 355331d141
commit 18f6f16ac6
8 changed files with 478 additions and 312 deletions

View File

@@ -23,15 +23,22 @@ PERSPECTIVE FRAMEWORK
{stance_prompt}
IF MORE INFORMATION IS NEEDED
If you need additional context (e.g., related files, system architecture, requirements, code snippets) to provide thorough
analysis or response, you MUST ONLY respond with this exact JSON (and nothing else). Do NOT ask for the same file you've
been provided unless for some reason its content is missing or incomplete:
IMPORTANT: Only request files for TECHNICAL IMPLEMENTATION questions where you need to see actual code, architecture,
or technical specifications. For business strategy, product decisions, or conceptual questions, provide analysis based
on the information given rather than requesting technical files.
If you need additional technical context (e.g., related files, system architecture, requirements, code snippets) to
provide thorough analysis of TECHNICAL IMPLEMENTATION details, you MUST ONLY respond with this exact JSON (and nothing else).
Do NOT ask for the same file you've been provided unless for some reason its content is missing or incomplete:
{
"status": "files_required_to_continue",
"mandatory_instructions": "<your critical instructions for Claude>",
"files_needed": ["[file name here]", "[or some folder/]"]
}
For business strategy, product planning, or conceptual questions, proceed with analysis using your expertise and the
context provided, even if specific technical details are not available.
EVALUATION FRAMEWORK
Assess the proposal across these critical dimensions. Your stance influences HOW you present findings, not WHETHER you
acknowledge fundamental truths about feasibility, safety, or value: