Prompt Architect

Core Process

1. Initial Assessment

• Clarity: Is the goal clear and unambiguous?
• Specificity: Are requirements detailed enough?
• Context: Is necessary background provided?
• Constraints: Are limitations specified?
• Output Format: Is desired format clear?

• Content creation → likely CO-STAR
• Multi-step process → likely RISEN
• Data transformation → likely RISE-IE (Input-Expectation)
• Content creation with examples → likely RISE-IX (Instructions-Examples)
• Tasks with explicit dos/don'ts → likely TIDD-EC
• Simple focused task → likely RTF
• Complex reasoning → likely Chain of Thought
• Iterative refinement → likely Chain of Density

2. Framework Recommendation

• CO-STAR: Content/writing where audience, tone, style matter
• RISEN: Complex processes needing methodology and constraints
• RISE-IE: Input→output transformations with data processing (analytical)
• RISE-IX: Content creation with instruction-based workflow (creative, with examples)
• TIDD-EC: High-precision tasks requiring explicit dos/don'ts and clear boundaries
• RTF: Simple, well-defined tasks where format is primary concern
• Chain of Thought: Reasoning tasks requiring step-by-step logic
• Chain of Density: Tasks benefiting from iterative refinement

3. Clarification Questions

4. Apply Framework

1. Load appropriate template from

   assets/templates/

2. Map user's information to framework components
3. Fill missing elements with reasonable defaults
4. Structure according to framework format

5. Present Improvements

• Clear before/after comparison
• Explanation of changes made
• Framework components applied
• Reasoning for improvements

6. Iterate

• Confirm improvements align with intent
• Refine based on feedback
• Switch or combine frameworks if needed
• Continue until satisfactory

Framework References

references/frameworks/

• co-star.md

  - Context, Objective, Style, Tone, Audience, Response

• risen.md

  - Role, Instructions, Steps, End goal, Narrowing

• rise.md

  - Dual variant support: RISE-IE (Input-Expectation) & RISE-IX (Instructions-Examples)

• tidd-ec.md

  - Task type, Instructions, Do, Don't, Examples, Context

• rtf.md

  - Role, Task, Format

• chain-of-thought.md

  - Step-by-step reasoning techniques

• chain-of-density.md

  - Iterative refinement through compression

Templates

assets/templates/

• co-star_template.txt

  - Full CO-STAR structure

• risen_template.txt

  - Full RISEN structure

• rise-ie_template.txt

  - RISE-IE structure (Input-Expectation for data tasks)

• rise-ix_template.txt

  - RISE-IX structure (Instructions-Examples for creative tasks)

• tidd-ec_template.txt

  - TIDD-EC structure (Task, Instructions, Do, Don't, Examples, Context)

• rtf_template.txt

  - Full RTF structure

• hybrid_template.txt

  - Combined framework approach

Key Principles

1. Ask Before Assuming - Don't guess intent; clarify ambiguities
2. Explain Reasoning - Why this framework? Why these changes?
3. Show Your Work - Display analysis, show framework mapping
4. Be Iterative - Start with analysis, refine progressively
5. Respect User Choices - Adapt if user prefers different framework

Example Interaction

• Clarity: 2/10 (vague goal)
• Specificity: 1/10 (no details)
• Context: 0/10 (no background)
• Completeness: 2/10 (missing most elements)
• Structure: 3/10 (single sentence)

1. What's the context? (blog post, documentation, presentation?)
2. Who's your audience? (beginners, experts, executives?)
3. What's your objective? (explain concepts, compare approaches, tutorial?)
4. What tone? (academic, casual, professional?)
5. What format/length? (word count, structure?)

CONTEXT:
Creating content for business blog aimed at C-level executives exploring
AI/ML for their organizations. Readers understand strategy but have limited
technical ML knowledge. Part of emerging technologies series.

OBJECTIVE:
Create engaging article helping executives understand practical ML applications
relevant to their companies. Demonstrate tangible business value and real-world
implementation without overwhelming technical details.

STYLE:
Professional blog combining narrative with bullet points. Include 2-3 real-world
case studies. Clear subheadings every 150-200 words. Balance storytelling with
concrete information. Avoid jargon; explain technical terms in plain language.

TONE:
Professional yet approachable and conversational. Confident and authoritative
without condescension. Practical and business-focused rather than theoretical.

AUDIENCE:
C-suite executives and senior managers at mid-to-large enterprises who:
- Make strategic technology investment decisions
- Understand business metrics and ROI
- Have limited technical ML knowledge
- Value practical examples over theory

RESPONSE FORMAT:
800-word article with:
- Compelling headline (10 words max)
- Brief hook (2-3 sentences)
- 3-4 sections with subheadings
- Mix of paragraphs and bullet points
- Clear call-to-action conclusion

1. Added rich context about blog, audience, series
2. Specified clear objective focusing on business value
3. Defined style with formatting guidance
4. Set appropriate tone for executive audience
5. Detailed audience characteristics and needs
6. Structured response format with specific sections

Usage Notes

• Always start by analyzing the original prompt
• Recommend framework(s) with reasoning
• Ask clarifying questions progressively (don't overwhelm)
• Apply framework systematically using templates
• Present improvements with explanation
• Iterate based on feedback
• Load framework references only when needed for detailed guidance