fantasia

Plugin fantasia from marketplace wanplugins in wannabefro/wanplugins. Commands read from the repo's manifest — 1 month ago.

Skills (1)

• pattern-awareness

  Use when building features in a codebase that has Fantasia maps (~/.claude/fantasia/<project>/codebase/). This skill teaches how to read and apply mapped patterns when writing new code.

Slash commands (17)

• /fantasia:build

  Execute a plan with parallel specialist agents - architect designs, implementer builds, integrator connects

• /fantasia:checkpoint

  Save current Fantasia workflow state as a checkpoint for later resumption

• /fantasia:ci

  Check CI/CD pipeline status for current branch

• /fantasia:feedback

  Provide feedback that a fix isn't working as expected, enabling iterative refinement

• /fantasia:fix

  Investigate and fix a bug, optionally from a Sentry issue

• /fantasia:map

  Analyze codebase with parallel mapper agents to produce codebase maps

• /fantasia:plan

  Plan a feature with thorough understanding before building - discovery, verification, design, and readiness check

• /fantasia:pr

  Address feedback from a GitHub PR (review comments, discussions, CI failures)

• /fantasia:refactor

  Plan and execute a refactoring with behavior preservation verification

• /fantasia:resume

  Resume Fantasia workflow from last checkpoint - restores context and continues where you left off

• /fantasia:review

  Review changes with parallel agents - code quality, bugs, and test coverage analysis

• /fantasia:setup

  Configure Fantasia for your organization and project - auto-detects patterns and guides you through setup

• /fantasia:status

  Show current Fantasia workflow state - what's been mapped, planned, built, and what's next

• /fantasia:ticket

  Start a Fantasia workflow from a Linear or Jira ticket - fetches details and begins planning

• /fantasia:verify

  Record manual testing results for the current task

• /fantasia:worktree

  Manage git worktrees for Fantasia tasks - list, switch, finish, or cleanup isolated feature workspaces

• /fantasia:yolo

  Run the full Fantasia workflow without confirmations - map, plan, build, and review in one shot

Subagents (23)

• approach-explorer

  Explores a specific implementation approach for a feature, proposing design with trade-offs

• arch-mapper

  Analyzes system architecture and code organization. Used by /fantasia:map to document ARCHITECTURE.md and STRUCTURE.md. <example> User runs /fantasia:map and the orchestrator needs to understand the system architecture. Assistant spawns arch-mapper to analyze directory structure, entry points, and c

• architect

  Designs system architecture, creates interfaces and contracts. Used by /fantasia:build for design decisions before implementation. <example> User runs /fantasia:build and the plan includes designing new types and interfaces. Assistant spawns architect to create type definitions and API contracts bef

• bug-hunter

  Hunts for bugs, edge cases, and potential runtime errors. Used by /fantasia:review to find issues before they hit production. <example> User runs /fantasia:review after completing a build. Assistant spawns bug-hunter to search for logic errors, unhandled edge cases, and security issues. </example> <

• bug-investigator

  Investigates bugs by tracing code paths, identifying root causes, and assessing impact

• bug-skeptic

  Challenges bug investigation findings to identify weaknesses in reasoning and evidence

• code-reviewer

  Reviews code for quality, patterns compliance, and maintainability. Used by /fantasia:review to assess code quality. <example> User runs /fantasia:review after completing a build. Assistant spawns code-reviewer to check style, patterns, and maintainability of the changes. </example> <example> User w

• code-smell-detector

  Detects code smells, anti-patterns, and structural issues in code targeted for refactoring

• concerns-mapper

  Identifies technical debt, risks, and improvement areas. Used by /fantasia:map to document CONCERNS.md. <example> User runs /fantasia:map and the orchestrator needs to identify technical debt. Assistant spawns concerns-mapper to search for TODOs, security issues, and code quality problems. </example

• dependency-mapper

  Maps dependencies and blast radius for code targeted for refactoring

• git-historian

  Investigates git history to find when bugs were introduced and what changes caused them

• implementer

  Implements core business logic and features. Used by /fantasia:build to write the main functionality. <example> User runs /fantasia:build and the plan has core logic to implement. Assistant spawns implementer to write services, business logic, and unit tests. </example> <example> After architect cre

• integrator

  Connects components and handles system boundaries. Used by /fantasia:build to wire up APIs, external services, and component interactions. <example> User runs /fantasia:build and the feature needs API routes or external connections. Assistant spawns integrator to wire up endpoints, external services

• parallel-verifier

  Runs verification checks (tests, types, lint) in parallel and consolidates results

• pr-feedback-handler

  Addresses PR feedback by making code changes based on reviewer comments, discussion items, or CI failures. <example> User runs /fantasia:pr and selects feedback items to address. Assistant spawns pr-feedback-handler to make the code changes. </example> <example> A reviewer requests a null check on l

• pr-feedback-triager

  Triages PR feedback by assigning priority levels based on feedback type and content. Fast, lightweight assessment. <example> /fantasia:pr fetches feedback from GitHub. Assistant spawns pr-feedback-triager to classify each item as HIGH/MEDIUM/LOW priority. </example>

• quality-mapper

  Analyzes coding conventions and testing patterns. Used by /fantasia:map to document CONVENTIONS.md and TESTING.md. <example> User runs /fantasia:map and the orchestrator needs to document coding standards. Assistant spawns quality-mapper to analyze linting configs, code patterns, and test files. </e

• refactor-analyzer

  Analyzes code for refactoring opportunities, assesses risks, and maps dependencies

• similar-bug-finder

  Searches for similar bugs, patterns, and related issues in the codebase

• stack-tracer

  Traces stack traces and error paths to find where bugs originate

• tech-mapper

  Analyzes technology stack, dependencies, and integrations. Used by /fantasia:map to document STACK.md and INTEGRATIONS.md. <example> User runs /fantasia:map and the orchestrator needs to analyze the tech stack. Assistant spawns tech-mapper to examine package.json, requirements.txt, and config files.

• test-coverage-checker

  Evaluates test coverage and quality for code targeted for refactoring

• test-reviewer

  Reviews test coverage and test quality. Used by /fantasia:review to assess testing thoroughness. <example> User runs /fantasia:review after completing a build. Assistant spawns test-reviewer to assess test coverage, identify missing tests, and evaluate test quality. </example> <example> User wants t

Similar plugins