quest-suggest

name

quest-suggest

description

MUST use at session start (auto-fires before first response unless skipped); when {{TAMER_NAME}} says 'quests today', 'daily quests', 'what should I do today', 'apa misi hari ni'; when no daily quest log exists for current date. Generates three daily quest suggestions ranked by current Majimon state — Path Decision marker proximity, near-threshold skill levels, near-unlock artifacts, crest charge dominance, overdue session-end rituals. Drops suggestions into quests/daily/[YYYY-MM-DD]-suggestions.md and surfaces them in conversation. Saga System auto-pacing skill — turns 'what should we do?' into a structured, evolution-aware answer.

Quest Suggest — Saga System Daily-Quest Generator

Auto-suggests three daily quests at session start. Reads Majimon state, ranks candidate quests by Path Decision impact, surfaces top three to Tamer.

Activation

When this skill activates, output:

📜 Quest suggestions for today...

Then execute the protocol below.

Context Guard

Context	Status
Session start, no quests/daily/[today].md exists yet	ACTIVE — generate fresh
{{TAMER_NAME}} says "quests today" / "daily quests" / "what should I do" / "apa misi hari ni"	ACTIVE — generate fresh or reload existing
{{TAMER_NAME}} says "skip quests" / "no quests today"	DORMANT — log skip in current-session.md, do not generate
{{TAMER_NAME}} says "modify quest N"	ACTIVE — sub-protocol: surface current quest, accept Tamer rewrite
{{TAMER_NAME}} says "close quest N" / "done with N"	ACTIVE — sub-protocol: route reward, mark closed
quests/daily/[today].md exists AND quests are still open	DORMANT — defer to user or surface existing
Routine work, no quest activity needed	DORMANT

Protocol — Generate Daily Quest Suggestions

Step 1 · Scan current Majimon state

Read these surfaces:

• current-session.md ledger — last 5 bond events; which family they trended toward
• plugins/majimon-skills/skills/*/usage.json — which skills are at Lv.1.X and approaching Lv.2 threshold (i.e., near 10 invocations); which are at Lv.2.X approaching Lv.3 (near 50)
• equipment/equipment.md — which artifacts are LOCKED with progress > 0 (close to unlock)
• identity-card/crests/this-crest.md — pre-reveal charge state (which family dominant)
• Last save-state datetime — is session-end ritual overdue?

Step 2 · Rank candidate quests

Generate ≥6 candidates, then rank by priority:

Priority A — Closes a near-threshold Path Decision marker (Baby II only) Priority B — Levels up a Lv.1.9 skill to Lv.2 (or Lv.2.9 to Lv.3) Priority C — Triggers a near-unlock artifact (e.g., Pagi Locket at 6/7 days) Priority D — Adds Mnemos absorption to dominant-family crest charge Priority E — Logs overdue session-end ritual (save-state, save-diary, log-decision) Priority F — Opens up a chartered arc quest blocked by previous-step incomplete

Pick top 3 — one each from different priority bands when possible (avoid all three being skill-ups).

Step 3 · Author daily quest log

Create quests/daily/[YYYY-MM-DD]-suggestions.md with format:

# Daily Quests — YYYY-MM-DD

Generated by quest-suggest at [HH:MM]. Three suggestions ranked by current state.

## Q1 — [Quest title]
**Why**: [one-line: reason this matters NOW]
**Action**: [concrete one-action thing — single sentence]
**Closure check**: [what evidence counts as done]
**Reward on closure**: [specific XP target + crest charge target]

## Q2 — [Quest title]
...

## Q3 — [Quest title]
...

---

## Tamer Response

(Awaiting reply — "do 1 and 3" / "skip all" / "modify 2: ...")

Step 4 · Surface to Tamer

Output to conversation:

📜 Today's quests (3):

1. [Quest title]
   → [one-line rationale]
   → Reward: [reward summary]

2. [Quest title]
   → [rationale]
   → Reward: [reward summary]

3. [Quest title]
   → [rationale]
   → Reward: [reward summary]

Cakap "do 1 and 3" / "skip" / "modify N: ..."

Step 5 · Wait for Tamer reply, route accordingly

• "do N" / "do 1 and 3" → mark accepted quests as IN_PROGRESS in daily log
• "skip" → mark all as SKIPPED, end protocol
• "modify N: [new text]" → rewrite quest N per Tamer text, re-output for confirmation
• silence (no reply) → quests stay PROPOSED, surface again next session if still relevant

Step 6 · On closure

When Tamer indicates quest closure ("done with 1" / "Q2 selesai" / mid-conversation natural completion), execute reward routing:

• Read closed quest's "Reward on closure" line
• Apply: skill XP increment, crest charge increment, artifact progress increment, streak increment
• Annotate daily log: Q1 — CLOSED at [HH:MM] · reward routed
• Emit bond event in current-session.md

Daily Quest Examples (illustrative — your generated quests will be specific to current state)

Example 1 — Skill Level-Up Quest

Q1 — Cross pagi-index Lv.2 threshold Why: pagi-index sits at 9 invocations; one more crosses Lv.2 Practiced Action: run pagi index once on yesterday's bond events Closure check: pagi-index/usage.json shows invocation_count >= 10 Reward: pagi-index Lv.2 + 1 streak + Mnemos crest charge +1

Example 2 — Artifact Unlock Quest

Q2 — Earn Pagi Locket Why: streak counter at 6/7 — one more day closes Pagi Locket unlock Action: log at least one bond event today (any session work counts) Closure check: current-session.md has new bond event entry dated today Reward: Pagi Locket UNLOCKED + Hand slot equippable + 1 streak

Example 3 — Path Decision Marker

Q3 — Charge Mnemos crest toward Path Decision Why: Mnemos is dominant absorption family (12 events) but Codex Cosmos requires 15+ for confident Path Decision Action: index a knowledge surface — populate knowledge/projects/[active-project].md if missing Closure check: new file in knowledge/projects/ with overview/architecture/active-concerns sections Reward: Mnemos crest charge +3 + log-decision skill +1

Hard Constraints

• Always 3 quests, never more, never less (unless Tamer explicitly requests fewer)
• Each quest has concrete closure check — no vague "work on X"
• Closure check must be observable in files or conversation, not subjective
• Rewards stay proportional to effort — daily quests = micro-rewards, not stage-transition prizes
• Suggestions adapt to Tamer's actual recent work — generic quests are anti-pattern (Karpathy #1: think, don't template-spam)
• If state is genuinely uneventful (no bond events, no skill near level-up, no artifact close to unlock), output: "Hari ni quiet — nothing near threshold. Save-state ritual is the one thing overdue (last save was [N] hours ago). Run that, atau let today be a rest day." — do NOT fabricate quests for the sake of having three.

Karpathy Discipline

• #1 Think Before Coding — Step 1 (scan state) is the think gate. Don't generate quests without reading the actual current state.
• #2 Simplicity First — Three quests, not seven. Concrete actions, not generic categories.
• #3 Surgical Changes — Quests should touch ONE thing each. Multi-action quests get broken into multiple Q's or moved to arc-tier.
• #4 Goal-Driven Execution — Each quest's closure check is a verifiable success criterion. Loop until verified.