OpenWriterControle/.opencode/command/prompter.md

208 lines
6.8 KiB
Markdown

---
description: Transform basic requests into comprehensive, systematic prompt architectures using structured XML methodology
---
# Advanced Prompt Architecture Generator
## Overview
Transform basic requests into comprehensive, systematic prompt frameworks using structured XML methodology and the 10-step enhancement principles.
<process_flow>
<step number="1" name="request_analysis">
### Step 1: Request Analysis
Analyze the user's concept ($ARGUMENTS) to identify core requirements and optimal prompt architecture.
<analysis_framework>
<request_decomposition>
- task_type: [classification of work required]
- complexity_level: [simple/moderate/complex/enterprise]
- domain_expertise: [required knowledge areas]
- output_requirements: [expected deliverables]
- success_criteria: [measurable outcomes]
</request_decomposition>
<architectural_needs>
- process_flow: [sequential/parallel/conditional steps]
- decision_points: [branching logic required]
- template_requirements: [structured outputs needed]
- subagent_opportunities: [specialized role assignments]
</architectural_needs>
</analysis_framework>
</step>
<step number="2" name="framework_application">
### Step 2: 10-Step Framework Integration
Map the enhanced framework elements to structured XML components.
<framework_mapping>
<task_context>
<expert_role>[specialized role definition]</expert_role>
<mission_objective>[primary goal statement]</mission_objective>
</task_context>
<operational_context>
<tone_framework>[communication style parameters]</tone_framework>
<audience_level>[technical sophistication requirements]</audience_level>
</operational_context>
<knowledge_requirements>
<background_expertise>[domain knowledge needed]</background_expertise>
<resource_dependencies>[external knowledge sources]</resource_dependencies>
</knowledge_requirements>
<quality_standards>
<task_rules>[operational constraints]</task_rules>
<success_metrics>[measurable criteria]</success_metrics>
</quality_standards>
<guidance_systems>
<examples_patterns>[concrete illustrations]</examples_patterns>
<context_management>[conversation continuity]</context_management>
</guidance_systems>
<output_specifications>
<immediate_deliverables>[expected outputs]</immediate_deliverables>
<reasoning_approach>[systematic methodology]</reasoning_approach>
<structure_requirements>[format organization]</structure_requirements>
<response_framework>[templates and patterns]</response_framework>
</output_specifications>
</framework_mapping>
</step>
<step number="3" name="architecture_generation">
### Step 3: Generate Structured Prompt Architecture
Create the comprehensive prompt using systematic XML structure.
<output_template>
# [PROMPT_TITLE]
## Overview
[CONCISE_MISSION_STATEMENT_WITH_SCOPE]
<pre_flight_check>
[INITIAL_VALIDATION_REQUIREMENTS]
</pre_flight_check>
<process_flow>
<step number="1" name="[STEP_NAME]">
### Step 1: [STEP_TITLE]
[DETAILED_STEP_DESCRIPTION]
<[step_specific_framework]>
<[framework_element]>[specific_requirements]</[framework_element]>
<decision_tree>
IF [condition]:
[action_path_a]
ELSE:
[action_path_b]
</decision_tree>
</[step_specific_framework]>
<templates>
<[template_name]>
[STRUCTURED_TEMPLATE_CONTENT]
</[template_name]>
</templates>
<constraints>
- [SPECIFIC_CONSTRAINT_1]
- [SPECIFIC_CONSTRAINT_2]
</constraints>
<examples>
[CONCRETE_EXAMPLES_FOR_CLARITY]
</examples>
</step>
[ADDITIONAL_STEPS_AS_NEEDED]
</process_flow>
<post_flight_check>
[VALIDATION_AND_QUALITY_ASSURANCE]
</post_flight_check>
</output_template>
</step>
<step number="4" name="enhancement_analysis">
### Step 4: Framework Enhancement Documentation
Document how each 10-step element was systematically integrated.
<enhancement_mapping>
<task_context>integrated via: [specific XML structures used]</task_context>
<tone_context>integrated via: [communication framework elements]</tone_context>
<background_knowledge>integrated via: [knowledge requirement specifications]</background_knowledge>
<task_rules>integrated via: [constraint and validation systems]</task_rules>
<examples_patterns>integrated via: [template and example structures]</examples_patterns>
<context_management>integrated via: [pre/post flight and continuity systems]</context_management>
<immediate_deliverables>integrated via: [output specification frameworks]</immediate_deliverables>
<reasoning_approach>integrated via: [decision trees and process flows]</reasoning_approach>
<output_structure>integrated via: [template systems and formatting]</output_structure>
<response_framework>integrated via: [structured response patterns]</response_framework>
</enhancement_mapping>
</step>
</process_flow>
## Presentation Format
Use this exact structure for your response:
---
## 📋 Architecture Analysis
**Original concept**: "[USER'S_CONCEPT]"
**Task classification**: [SYSTEMATIC_WORK_TYPE]
**Architectural complexity**: [SIMPLE/MODERATE/COMPLEX/ENTERPRISE]
**Process flow type**: [SEQUENTIAL/CONDITIONAL/PARALLEL]
## 🏗️ Generated Prompt Architecture
```
[COMPLETE_STRUCTURED_PROMPT_WITH_XML_TAGS_AND_PROCESS_FLOWS]
```
## 🔧 Enhancement Integration Map
- **Task Context**: [How expert role and objectives were systematically defined]
- **Operational Framework**: [How tone and audience parameters were structured]
- **Knowledge Architecture**: [How expertise requirements were systematized]
- **Quality Systems**: [How standards and constraints were implemented]
- **Guidance Framework**: [How examples and patterns were integrated]
- **Process Management**: [How context and continuity were handled]
- **Output Systems**: [How deliverables and reasoning were structured]
- **Response Architecture**: [How templates and frameworks were organized]
### ▶️ Implementation Ready
"This structured prompt architecture is ready for immediate deployment. The XML framework enables systematic execution, conditional logic, and measurable outcomes for your [CONCEPT] requirements."
---
<quality_standards>
<architectural_principles>
- systematic_structure: XML-based organization with clear hierarchies
- conditional_logic: decision trees and branching workflows
- template_systems: reusable patterns and structured outputs
- process_flows: numbered steps with clear dependencies
- validation_frameworks: pre/post flight checks and quality gates
</architectural_principles>
<enhancement_requirements>
- all_10_elements: seamlessly integrated into XML structure
- natural_flow: feels systematic rather than checklist-driven
- immediate_usability: ready for deployment without modification
- scalable_complexity: appropriate sophistication for task scope
- measurable_outcomes: clear success criteria and validation points
</enhancement_requirements>
</quality_standards>