epicsagas
UserAI-native publishing system — build books like software. 6-phase pipeline from blank page to EPUB/PDF, with 16 skills, 7 agents, and 8 genre templates. Claude Code plugin.
Categories
Indexed Skills (49)
book-academic
Academic writing patterns — IMRAD structure, literature review, argument chains, citation practices, thesis/dissertation layout.
book-game
Game scenario patterns — quest/event trees, branching dialogue, world-building, character arcs across routes, lore bibles.
book-genre-creator
Meta-skill that references all available genres, agents, and skills to help users define and create any genre — including custom genres not yet supported.
book-poetry
Poetry patterns — form types (sonnet/haiku/free verse), stanza structure, meter/rhythm, imagery systems, collection architecture.
loom
AI-native publishing system: autonomous multi-phase workflows from ideation to export. Fiction, non-fiction, and technical books. Trigger: /velith or book-related requests.
discover
Trigger: vague/unfocused request or solution-without-problem. Also invoked via /discover command. Reframes goal before acting.
orchestrate
Trigger: active multi-agent run. Handles inbox reading, dep resolution, message formatting, handoffs. Also provides status dashboard and intervention control via internal modes.
book-status
Book project status and progress dashboard. Writes status.json for the web UI.
alcove
HTTP API-based documentation server (always running). Questions about project architecture, conventions, decisions, code structure, tech debt, env config, progress, or doc health. Also: init project, audit docs, lint, validate, promote note, rebuild index, search vaults.
book-draft
Phase 3: Drafting. Plan-Then-Execute chapter generation with parallel writing and continuity validation.
book-edit
Phase 4: Editing. 5-stage pipeline — editorial assessment, developmental edit, line edit, copy edit, proofread.
book-fiction
Fiction-specific patterns — Save the Cat! 15-beat, Snowflake Method, Hero's Journey, character bible, scene structure.
book-ideation
Phase 1: Ideation. Concept validation, market gap analysis, competitive matrix, final concept selection.
book-init
Phase 0: Onboarding. Initialize new book project — define genre, audience, language, scope, generate PRD.md and STYLE.md.
book-nonfiction
Non-fiction patterns — problem-solution structure, learner personas, evidence hierarchy, argument structure, chapter template.
book-outline
Phase 2: Outlining. Apply genre-specific structures, generate per-chapter specs, cross-reference map, structural validation.
book-publish
Phase 5: Publishing. Convert to EPUB/PDF/MOBI/TXT/Markdown, cover design, metadata, title candidates, KDP checklist, marketing plan.
book-screenplay
Screenplay patterns — 3-act film structure, sequence method, scene/cut formatting, dialogue rules, A/B story weaving.
book-technical
Technical book patterns — concept progression gradient, code block rules, diagrams, API reference format, lab design.
_dispatch
Core router. Always active. Auto-invokes matching skill before every response. Runs confusion protocol on high-risk ambiguity.
agent-introspection
Loop-breaking self-diagnosis. Use when 3+ consecutive failures occur, circular retries persist, or context overwhelms the session.
audit
Audit phase. Parallel review: code quality + security + tests. Semantic dedup of cross-mode findings. Outputs PASS/WARN/FAIL per dimension. Validates spec coverage.
check
Check phase. Launches parallel review (code quality + security + tests) with scope-based extras (API contract, accessibility, migration safety). Outputs PASS/WARN/FAIL per dimension with spec coverage verification.
commit
Conventional Commits 1.0 generator. Stages relevant files, infers type(scope): description, never uses --no-verify.
context
Context window manager. Snapshots session state, compacts conversation, and resumes via hook. Use when context exceeds 70% or a large new task begins.
council
4-voice parallel deliberation (Architect · Skeptic · Pragmatist · Critic) for architecture, tech selection, or design decisions with no clear answer. Anti-anchoring: each voice gets independent context. Records decision in harness-mem.
debug
Systematic root-cause isolation for test failures, runtime errors, or unexpected behavior. Narrow hypothesis → verify → fix.
document
Documentation generator for public APIs, functions, and modules. Use when exports, signatures, or new modules are added or changed.
eval
Quality and performance evaluation with baseline comparison. Sub-modes: correctness, performance, quality, regression. Outputs PASS/WARN/FAIL per dimension. Use for pre-ship evaluation or regression checks.
evolve
Ring 3 evolution engine. Analyzes session observations, generates and improves evolved skills, shows metrics dashboard. Subcommands: status, history, rollback, reset. Use for post-session review and skill improvement.
go
Go phase. Reads the approved SPEC file, maps Requirements to tasks (plan), executes via TDD (build), and integrates results verifying all Acceptance Criteria.
orbit
State-persisted autonomous pipeline: spec → go → audit → eval → ship → evolve in one command. Auto-detects direct/council/interactive mode. Crash-recoverable via PIPELINE-*.json. Hands-off until PR.
perf
Performance optimizer for loops, DB queries, rendering, and batch operations. Catches N+1 queries, missing indexes, and unnecessary re-renders.
reflect
On-demand human self-assessment of AI usage quality. Scores 5 dimensions from session data. Not agent performance review.
secure
Security review checklist with optional engagement scoping. Use when auth, DB, API, infra, or secrets code is touched.
ship
Ship phase. Runs isolated integration test in a fresh worktree, creates a PR with full spec + check report in the body, watches CI, and auto-fixes failures.
simplify
Code simplification for high-complexity files. Targets deep nesting, copy-paste patterns, god functions, and files over 200 lines.
spec
Spec phase. Converts user requirements into a numbered Requirements + Acceptance Criteria document saved as SPEC-{timestamp}.md. Prompts /team suggestion when 3+ requirements are detected.
tdd
Test-Driven Development enforcer. Red→Green→Refactor cycle with no production code without a failing test first. Use for new features and bug fixes.
threat-model
Threat modeling and attack surface analysis. Use when assessing security boundaries, modeling threat actors, or generating threat scenarios.
triage
Adversarial validation of vulnerability findings. Use when triaging security findings, validating vulnerabilities, or prioritizing remediation.
verify
Pre-merge verification gate. Build, test, and lint must all pass before marking done or shipping.
vuln-scan
Systematic vulnerability scanner across injection, auth, data exposure, and dependencies. Use when scanning for vulnerabilities, reviewing security, or validating threat models.
team
Org-level agent team designer via `epic team` CLI (cross-project, append-merge). Subcommands: list, show, sync, link, unlink, history. Use when setting up agents, designing teams, or /spec yields 3+ requirements.
code-reviewer
Code smell detector and refactoring advisor. Triggers on: file path mentioned, 'review this code', 'find smells', 'analyze', 'refactor', or code shared. Calls Episteme HTTP API (analyze + refactor endpoints) immediately. Outputs smell table, ranked refactorings, principle violations.
episteme-researcher
Use this agent when you need to explore or research software engineering knowledge — finding design patterns, refactorings, laws, and code smells, or mapping relationships between concepts in the Episteme knowledge graph.
episteme
Software engineering knowledge graph — patterns, laws, refactorings, smells. Activates on any code quality concern, design decision, architecture review, or engineering question — even when the user describes problems informally. Uses Episteme HTTP API (resolved via `epis api env`) via curl.
architecture-analyst
Use this agent when you need to evaluate a system architecture or technology decision — identifying scalability risks, structural smells, law violations (Conway, Amdahl, Gall), and design pattern misuse using the Episteme knowledge graph.
episteme-advisor
Use this agent when the user faces an engineering decision, trade-off, or architecture question — choosing between patterns, resolving design conflicts, or applying refactorings. Grounds every recommendation in the Episteme knowledge graph.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.