fusion-tea: Skill for Claude Code

Before executing this skill, read .agentic-mbse/claude.md in Claude Code or .agentic-mbse/codex.md in Codex. Resolve supporting paths from this skill’s installed directory; keep generated outputs in the project or a temporary directory. Read referenced skills from .agents/skills/<name>/SKILL.md when their guidance is needed.

Narrate Goal

Create one human-readable account of what a goal's evidence supports at one cutoff. The narrative explains the starting problem, causal changes, measured results, limits, and useful visuals without becoming part of /run-goal.

Authority boundary

The narrative is derived presentation material. It is never evidence, state, authorization, a decision record, a review verdict, or an input cited by an authoritative artifact. If the narrative and a cited source disagree, the source wins.

Read from work/orchestration/goals/<goal-slug>/, but write only one new file under work/narratives/. Do not edit the goal, its evidence, native workflow records, earlier narratives, or project status files.

Intake and output

Get the canonical goal slug or goal-directory path from the request. Ask only if the target is missing or ambiguous. Confirm that goal.md, trail.md, and learnings.md exist.

Use the generation time in UTC and name the output work/narratives/YYYYMMDD-HHMMSSZ-<canonical-goal-slug>.md. Normal creation must not overwrite an existing file. If that exact path already exists, stop and report the collision.

Establish the source basis

1. Record the base commit with git rev-parse HEAD and the UTC generation time.
2. Read goal.md, then trail.md, then learnings.md. Follow the authoritative native records they cite when those records are needed to support the story.
3. Determine goal-level closure from the authoritative trail. A closed round, an accepted learning, or a review that recommends closure does not close the goal. Treat the goal as closed only when the trail records the owner's close ruling; current goals use a ## Goal close — YYYY-MM-DD heading. Otherwise report it as open at this cutoff.
4. For a closed goal, take the calendar date and disposition from the close entry. If that entry has no explicit time, find the commit that first introduced its close heading and use the commit time only as a rough proxy. Label it Git commit-time proxy and include the short commit id. If the entry is uncommitted or its introducing commit cannot be identified, state that the rough time is unavailable; never infer one from nearby work.
5. Do not use an earlier narrative, CURRENT_WORK.md, SUMMARY.md, or other orientation prose as evidence. They may help locate a source, but every retained claim must resolve to a goal file or native record.
6. Check the goal files and every cited native record actually used with git status --short -- <paths> immediately before writing. If relevant files changed while drafting, reread them before creating the snapshot.
7. Dirty sources are allowed. When any relevant input is dirty, label the cutoff Provisional, record the base commit, state that uncommitted source content was included, and say that the exact source state may not be recoverable from Git.