haowjy

Prose-level immersion patterns for narrative fiction. Use when writing or revising prose: the sentence-level and paragraph-level craft that pulls readers into the story. Project-specific voice comes from style files passed alongside this skill.

Adversarial reading methodology for narrative fiction: find what doesn't work, not confirm what does. Focus-area driven with dedicated resources per area. Use when reviewing drafts, evaluating prose quality, or assessing changes at any stage.

Arc structure, narrative design, and pacing at multiple scales: saga, arc, chapter, scene. Use when structuring story at any level, planning arcs, designing chapter outlines, or evaluating whether narrative structure serves the story's goals.

Team composition for writing workflows: which agents to spawn, how many, what focus areas to assign, and how to scale effort. Use when composing critic panels, dispatching researchers, staffing draft/revise loops, or setting up brainstorm fan-outs.

Story brainstorming capture: minimal notes that preserve creative freedom. Use when exploring narrative ideas, discussing characters, planning chapters, or thinking through story possibilities.

Logging and referencing writing issues: craft problems, tics, inconsistencies, and structural concerns found during analysis, critique, or review. Use when an agent identifies something worth tracking beyond a single critique report: repeated tics across chapters, inconsistencies that affect multiple scenes, structural problems that need the author's attention, or patterns that should be fixed in revision.

Load when producing any written artifact for humans.

How to build scenes: entry, dialogue, pacing, transitions. Use when writing or evaluating how scenes work on the page.

Load into any agent that receives human direction. Use before acting on instructions, recording decisions, or producing artifacts.

Load when establishing shared vocabulary, resolving term conflicts, disambiguating domain terminology, or auditing consistency across a project's vocab. Shared vocabulary is the contract between human intent and agent action — ambiguity is the root failure mode, vocab files are the record.

Load when reading from, writing to, or maintaining the KB. Covers layer model, structural conventions, and operational tooling.

Use when mining conversation history during dev work — recovering decisions from the top-level primary session, delegating bulk transcript reading to an explorer, or discovering all sessions tied to a work item across interruptions.

Use whenever you need to delegate work to another agent, run tasks in parallel, coordinate multiple agents, or inspect spawn outputs. Also use when routing work to a specific model or provider.

Load before spawning subagents to protect focus and role fit. Make sure to re-read the available agents before spawning a subagent; choose the most specific owner instead of broad defaults, then write a tight handoff with only the context that subagent needs.

Load when producing any written artifact for humans.

Load when a workspace may contain changes from humans or other agents. Covers safe orientation, preserving unfamiliar files, and containing outputs.

Multi-model supervisor that discovers skills, picks models, and composes runs. Use when executing multi-step plans across multiple models.

Agent execution engine that composes prompts, routes models, and writes run artifacts. Use when launching subagent runs.

Multi-model supervisor that discovers skills, picks models, and composes runs. Use when executing multi-step plans across multiple models.

Agent execution engine that composes prompts, routes models, and writes run artifacts. Use when launching subagent runs.

Verifies implementation aligns with stated requirements and acceptance criteria. Use before implementation (to clarify scope) and before final sign-off (to detect gaps).

Breaks the next task from a plan into an implementable task file. Use when decomposing a multi-step plan into ordered work units.

Explores codebases and evaluates approaches before planning. Use when investigating a problem space, comparing alternatives, or gathering context for a plan.

Reviews code against project rules and curated reference files. Use when auditing files for violations, reviewing changes, or generating cleanup tasks.

Load when writing or reviewing agent .md files. Design guidance for agent definitions and meridian-specific conventions.

Load when writing, reviewing, or improving any prompt artifact. Research-backed principles across four levels: prompt craft, skill extraction, agent design, and multi-agent coordination.

Load when reviewing agent definitions or skill content. Adversarial review methodology — finding quality, severity, and structured reporting.

Load when writing or reviewing skills. Design guidance for SKILL.md files and bundled resources.