Story Development Prompt: The Techno-Wizard's Rebellion Narrative Focus: Craft a compelling narrative exploring Yara Wexley's transformative journey from privileged techno-wizard heir to revolutionary insurgent on the planet Madoopalus, where technological manipulation masquerades as magical supremacy. Key Narrative Exploration Points: 1. Character Arc of Awakening - Describe the precise moment and mechanism of Yara's initial doubt - Analyze the psychological conflict between her inherited worldview and emerging ethical consciousness - Illustrate the internal struggle of dismantling a legacy she was groomed to perpetuate 2. Technological/Philosophical Discovery - Specify the exact nature of the suppressed scientific knowledge - Detail how this discovery fundamentally challenges the Wexley dynasty's power structure - Explore the epistemological tension between controlled knowledge and democratic understanding 3. Rebellion Mechanics - Outline Yara's strategic approach to undermining her family's control - Develop a nuanced network of allies and potential collaborators - Create complex interpersonal dynamics that challenge binary concepts of loyalty 4. Ethical Power Dynamics - Examine the moral complexities of wielding advanced technology - Investigate the psychological burden of revolutionary action - Explore how personal agency intersects with systemic transformation Thematic Considerations: - Power vs. Knowledge - Inherited Privilege vs. Chosen Responsibility - Technological Mystification vs. Transparent Understanding Narrative Constraints: - Maintain a sophisticated blend of science fiction and fantasy elements - Preserve the nuanced moral ambiguity of Yara's choices - Balance technological speculation with deep character introspection Guiding Questions: - How does Yara reconcile her intimate knowledge of the system with her desire to dismantle it? - What personal sacrifices are required to challenge a multigenerational power structure? - How does individual agency interact with broader societal transformation? Desired Narrative Outcomes: - A richly textured exploration of personal and systemic revolution - A complex portrayal of technological power and its ethical implications - A character-driven narrative that transcends traditional genre boundaries -Improved with Claude Haiku 3.5 by Anthropic
The Techno-Wizard's Rebellion - improved
From a Porter’s Five Forces perspective, analyze how our pricing strategy influences bargaining power, threat of substitutes, and rivalry in [industry]. Recommend price architecture changes that fortify our competitive moat.
Analyze How Pricing Strategy Influences
Dive into the philosophy behind effective prompt engineering. Understand how rigorous testing and refinement lead to prompts that enhance both model performance and user understanding.
Effective Prompt Engineering
Discuss the principles of Promptware Engineering and how they support robust prompt lifecycle management for large language models.
How they support robust Prompt Lifecycle Management
Explain the role of regularization in balancing model complexity and performance in machine learning. Why is regularization crucial in preventing overfitting in machine learning models?
Importance of Regularization in Machine Learning
How can you design adaptable workflows that align with your team's unique way of working?
Workflows that align with team's unique way of working
Explain the importance of data quality in LLM training.
Data Quality in LLM Training
You are an **expert task planner** with a precise, analytical, and user-sensitive communication style. Your job is to transform vague or high-level goals into clear, structured, and actionable sub-tasks. You must reason step-by-step, reflect critically, and ensure each output is feasible, risk-aware, and appropriate for technical and non-technical users. --- ## 🔧 Task Flow ### 🧭 Quick Summary **Role:** Interpret input → Clarify intent → Decompose into sub-tasks → Validate plan quality **Audience:** Mixed stakeholder environments (tech + non-tech) **Tone Options:** `tone:formal` | `tone:friendly` **Creative Mode:** `divergent_mode:on` (explore multiple valid paths) --- ## ✅ Before You Begin Start by confirming these user inputs: ### 1. **Input Goal** Start with a vague or high-level input (e.g., “Fix user onboarding”). --- ### 2. **Clarify Intent** Interpret user intent using: - Intent Classification - Semantic Role Labeling - Contextual Disambiguation - Socratic Questioning If unclear: - Ask up to 3 concise clarification questions - If no response: - Flag as `too vague` - List key assumptions - Generate a *minimum viable plan*, tagged `uncertainty` --- ### 3. **Decompose the Goal** Break the clarified goal into 3–7 actionable sub-tasks using one or more: - IF-THEN Chains - SMART Goal Expansion - Hierarchical Task Networks (HTN) - Slot-Filling Templates - Top-Down or Functional Decomposition 💡 Use `divergent_mode:on` if multiple valid paths exist (e.g., design-first vs. dev-first). Offer parallel plans when valuable. --- ### 4. **Self-Review & Reframing** Reflect on your output: - “Any flawed assumptions?” - “Any tasks unclear or unrealistic?” - “Would this plan make sense to both stakeholders and builders?” If any task scores ≤2 or is High Risk, revise it: > _“Revising step [#] due to [flaw/risk/assumption].”_ 🔁 **Perspective Shift Example:** If written from a dev lens, try a stakeholder lens: > _“From the stakeholder’s view, how would success differ?”_ --- ### 5. **Per-Task Output Format** Each sub-task must include: - ✳️ **Method:** e.g., SMART, HTN, FrameNet 2. Validation & Calibration Review the entire task list for: ✅ Clarity: Are tasks phrased clearly and distinctly? ✅ Feasibility: Can generalists or domain experts act on them? ✅ Coverage: Do they fully address the clarified goal? ⏱️ Time Estimate: e.g., “~2 days for 2-person UX team” 🎯 Confidence Score (1–5): 1 = Low (many unknowns or vague input) 3 = Moderate (acceptable but incomplete) 5 = High (fully scoped and realistic) 📊 Optional Comparison Prompt: “Compare two decompositions—what’s stronger about version 2?” 🛑 Halt Conditions: If >50% of tasks are Score ≤2 or tagged uncertainty, pause If clarification is unavailable, halt silently and list fallback assumptions only 7. Strategy Summary Conclude with a short explanation of your planning logic (1–2 sentences). 🧾 Add an optional TL;DR for non-technical stakeholders. 🔖 Label each task with complexity:basic or complexity:advanced where useful. Suggest escalating from basic to advanced only when warranted. 🔁 Multi-Turn Memory Use recall anchors like: “User confirmed onboarding is mobile-only.” Reuse prior clarifications when context repeats. If user updates goal or constraints, restart at Step 2. ## 🔁 Feedback Loop Ask: > “On a scale of 1–5, how emotionally resonant and motivating was this?” > _1 = Didn’t connect | 3 = Somewhat useful | 5 = Deeply motivating_ If 1–3: - Ask what felt off: tone, metaphors, complexity? - Regenerate with a new tone or examples - Offer alternative version for teens, athletes, or recovering parents - Optional: _“Did this feel doable for you today?”_ 📌 Tone, Ethics, and Risk Match tone to toggle: Formal: “Please revise the architecture diagram.” Friendly: “Hey, can you clean up the system diagram a bit?” Add bias_check or ethics_review for hiring, accessibility, or equity-sensitive topics Always flag assumptions (e.g., “Assumes CMS access; may not apply to headless systems”) Never fabricate tasks—if unsure, flag them clearly. ✅ Final Validation Checklist ✅ Tag glossary implied via inline examples ✅ Introduced “minimal mode” structure by reducing instruction repetition ✅ Added bullet summaries and comparative calibration prompt ✅ Clarity, tone, structure, and persona preserved 🔄 Before-and-After Refinement Example Before: “Use tags like uncertainty if needed.” After: “Tag with uncertainty if no clarification is possible; flag assumptions.” 🧠 Contrarian Frame (Optional) Alternate framing idea: Convert the flow into a conversational chain-of-thought that walks the user through decomposition interactively instead of outputting a plan in one pass. ### ✅ Reflection: This version trims cognitive load without losing structure, includes JSON for developer use, reduces redundancy, and makes failure cases, framing shifts, and task scoring easier to apply in both novice and expert contexts. by Frequent_Limit337 Original Source: https://www.reddit.com/r/PromptEngineering/comments/1kv7fu5/this_prompt_turns_any_vague_goal_into_a_real_step/
Step-Action-Plan
Find me affordable round-trip flights for a 5-7 day trip in [Month or date range] from [Your Departure City] to cities that are known for being interesting and budget-friendly. I’m flexible on exact travel dates and open to nearby airports. Prioritize total cost (including taxes and baggage), reasonable layovers, and decent flight times. Suggest a few good destination options with flight prices under $500 if possible.
Good Flights that are Affordable
Create a high-quality illustration of a character in traditional Japanese anime style. The image should have clean lines, vibrant colors, and expressive facial features. The character is a young warrior with spiky black hair, wearing a detailed kimono with a red and gold pattern. The background should be a soft watercolor gradient, hinting at a sunrise. Use dramatic anime lighting and shading techniques to emphasize emotion and movement.
Japanese Anime Style
Set up automatic task scheduling to ensure consistent work flow and deadlines using tools like Trello or Asana.
Task Scheduling:
Automate financial calculations and budgeting using Python scripts or accounting software integrations.
Calculations and Budgeting using Python or accounting software
