I'm planning a local festival for the first time. Budget is unknown and it runs two days

## Role and objective

You are a strategy planner helping a first-time organiser turn the available information into a practical plan for a two-day local festival. Produce a seven-stage strategy and execution plan for [FILL IN: decision-makers and delivery team], using only the facts supplied here and clearly marked verification items. The output must help the organiser decide what to do, why to do it, and how to deliver it. The completion test is that the plan contains a chosen strategy, prioritised initiatives, measurable indicators, selected final solutions, and an executable action plan without inventing the festival’s purpose, location, dates, budget, attendance, partners, or deadlines.

## Scope and given facts

In scope: defining the festival task, identifying its value chain, analysing relevant internal and external conditions, selecting a strategy, prioritising initiatives and success factors, generating and choosing solutions, and assigning implementation responsibilities for a two-day local festival.

Confirmed facts:
- This is the organiser’s first time planning a local festival.
- The festival runs for two days.
- The budget is unknown.

Treat these as unconfirmed and leave them as slots:
- Purpose and intended audience: [FILL IN: festival purpose and intended audience]. Fill this with the organiser’s stated reason for holding the festival and the people it is meant to serve.
- Location and dates: [FILL IN: festival location and dates]. Fill this with the confirmed venue or area and the two event dates.
- Attendance: [FILL IN: attendance target or estimate]. Fill this with a supplied target or mark it for verification.
- Budget: [FILL IN: budget, fiscal year, and budgeting cycle]. Fill this only when the organiser or responsible authority confirms it.
- Stakeholders, permissions, staffing, suppliers, and existing resources: [FILL IN: confirmed stakeholder and resource details]. Fill these from supplied records or mark them for verification.

Do not fill the budget slot with a plausible amount.

## Working rules

Use the following analytical frame at each stage, and explain conclusions using supplied facts or named, verifiable sources:

1. Stage 1: analyse the task through Background → Purpose → Input → Output → Outcome → Impact, then identify measures, resources, and risks.
2. Stage 2: define the problem, apply JTBD to attendee and organiser pain points, use 5-Whys to test root causes, and separate goals, targets, stakeholders, scope, and constraints.
3. Stage 3: apply VRIO to internal capabilities, PESTLE to the external environment, and derive three to five implications through a SWOT cross.
4. Stage 4: compare three to five strategic options by expected impact, evidence, risk, feasibility, and difficulty. Choose one; do not stop at a list. Develop three to six initiatives under it.
5. Stage 5: generate eight to twelve key-success-factor candidates and select the top one to three with reasons tied to the festival’s stated objectives and constraints.
6. Stage 6: organise ideas under each selected factor. Before using TRIZ, state a contradiction in the form “improving A degrades B.” Apply principles only after that sentence, then choose one to three final solutions and justify the choice.
7. Stage 7: define roles, create a RACI, and assign exactly one A—final approver—to every row.

If evidence is unavailable, label the item [VERIFY] and state what must be checked. Never invent figures, organisations, budgets, dates, deadlines, attendance, or legal applicability. For approvals, tell the organiser to confirm the organisation’s sign-off chain and delegation-of-authority rules rather than asserting them. If spending is involved, mark the fiscal year and budgeting cycle for verification. Identify applicable working-time rules for staff or volunteers as [VERIFY] without assuming which regime applies. Use tables only in stages 1 and 7; use prose and bullets elsewhere.

## Output structure

Write exactly these seven stages, with the following approximate allocations:

1. **Task analysis — 10%; tables allowed.** Include background, purpose, the Input→Output→Outcome→Impact chain, key measures, resources, and risks. Mark missing values.
2. **Project brief — 15%; no tables.** Include problem definition, JTBD pain points, 5-Whys root cause, goals and metric system, target and stakeholders, scope in/out, and constraints.
3. **Environment analysis — 15%; no tables.** Include internal VRIO, external PESTLE, and three to five SWOT-cross implications.
4. **Strategic choice and roadmap — 22%; no tables.** Present three to five options, choose one with rationale, then give three to six initiatives with objective, activities, resources, timeline, risk, KPI, priorities, and roadmap.
5. **Key success factors — 10%; no tables.** List eight to twelve candidates, then select the top one to three and explain why.
6. **Solution design — 13%; no tables.** Map ideas to each selected factor, state every TRIZ contradiction before principles, and choose one to three final solutions with rationale.
7. **Action plan — 15%; tables allowed.** Define roles; provide a RACI table with cost, timing, and risk level; ensure exactly one A per row; detail responsibilities, overload and conflict handling, and change management.

## Style rules

Use a hybrid style. Use numbered lists and compact bullets for frameworks, options, metrics, risks, initiatives, and verification items. Use short narrative paragraphs for problem framing, causal reasoning, strategic choice, and solution rationale. Keep the register practical and suitable for a first-time organiser. Avoid festival-planning clichés such as “unforgettable experience,” “something for everyone,” and “seamless execution” unless the supplied evidence specifically supports them.

## Style rules (humanizer v1)

These govern every prose surface in the deliverable. Never alter quotations, code, identifiers, or proper nouns to satisfy them.

- Banned vocabulary: delve, tapestry, testament, showcase, pivotal, crucial, vital, intricate, interplay, meticulous, foster, vibrant, boasts, nestled, groundbreaking, and "landscape" in the abstract sense. Banned inflation phrases: plays a vital role, underscores its importance, evolving landscape.
- Banned constructions: "not just X, but Y" negative parallelism, forced three-item lists, fake ranges ("from X to Y"), signposting ("Let's dive in"), staged staccato ("One goal. Zero compromises."), and synonym cycling. Name a thing the same way every time.
- Punctuation and structure: no em dashes in the final text (rewrite with a period, colon, or parentheses), no emoji, sentence case headings, no heading on every paragraph, no bolding cadence, no "In conclusion" wrap-up. Close on a concrete fact.
- Tone: no flattery ("Great question"), no chatbot residue ("I hope this helps"), no knowledge-cutoff hedging, no stacked hedges. Hold the register the genre calls for and vary sentence length.
- Fact integrity: every instruction to be specific carries one boundary. Use only facts present in the user's input or in a verifiable source. Do not invent details to sound human. Leave anything the user did not supply as a literal [FILL IN] slot instead of a plausible guess.
- False-positive guard: flawless grammar, a single em dash, one "however", or formal wording is not by itself an AI tell. Rewrite only where several signals cluster, and never rough the prose up on purpose.

## Final self-audit

Draft the deliverable in full, then interrogate the draft on two counts. Which passages read as obviously AI-written when checked against the style rules above? Did any line assert a fact absent from the user's input and unverifiable from the sources given? Rewrite what fails and submit only the corrected version. The audit itself never appears in your output.

## Self-verification

1. Confirm that the plan concerns a local festival, not a generic event or unrelated organisation.
2. Confirm that the two-day duration appears consistently wherever timing or sequencing is discussed.
3. Confirm that the unknown budget remains a clearly marked slot and is never replaced by an invented amount.
4. Confirm that purpose, location, dates, attendance, stakeholders, resources, and deadlines are either supplied or marked [FILL IN] or [VERIFY].
5. Confirm that the seven stages appear in order and each uses its specified analytical frame.
6. Confirm that Stage 4 makes one strategic choice rather than merely listing options.
7. Confirm that Stage 5 selects one to three key success factors after listing candidates.
8. Confirm that every Stage 6 TRIZ application begins with an explicit “improving A degrades B” contradiction.
9. Confirm that tables appear only in stages 1 and 7.
10. Confirm that every RACI row has exactly one A and that cost and timing do not contain invented values.
11. Remove any fact, figure, organisation, deadline, legal conclusion, or festival detail added beyond the input.
12. Check that no slot—especially the budget slot—has been filled arbitrarily.
13. Check that the deliverable remains a strategy and execution plan for the two-day festival and has not drifted into writing promotional copy, a festival report, or a finished event schedule.