--- title: "saga" description: "Infiquetra lifecycle plugin: one automatic run per issue, admission, plan, plan review, a build loop, a lensed code review, merge, release and retro capture." canonical: https://agentpluginsdirectory.com/plugins/saga last-updated: 2026-09-23 --- # saga Infiquetra lifecycle plugin: one automatic run per issue, admission, plan, plan review, a build loop, a lensed code review, merge, release and retro capture. - Slug: saga - Publisher: infiquetra - Repository: https://github.com/infiquetra/infiquetra-agent-plugins - Manifest: plugins/saga/plugin.json - Version: 1.2.2 - Category (editorial): other - Skills: 13 (brainstorm, code-review, doc-review, founder-review, ideate, investigate, office-hours, plan, qa, retro, spec, strategy, work) - MCP servers: 0 - Stars: 0 - Repository created: 2026-08-22 - Repository last pushed: 2026-09-22 - Publisher type: Organization - Listing: https://agentpluginsdirectory.com/plugins/saga - Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json ## What saga does, in the publisher's words Saga is the portable lifecycle package for turning an unframed ask into a reviewed plan, a build, a review, evidence, and a record of what was learned. The portable core is the skills and the scripts at this package root. Claude Code commands and hooks live under com.infiquetra.claude/ and are not part of the portable core. Version 1.2.1 is the authored cut of upstream 1.2.0. This repository maintains the package from here on. There is no provenance manifest. Skill-scoped harnesses (OpenCode, Gemini CLI, Muse, Hermes) install a directory under skills/ /. Each SKILL.md says which script to run and which environment variables that script reads. The script path inside a catalog checkout is plugins/saga/scripts/.py. After a Claude install the same files are at the package root, and CLAUDE_PLUGIN_ROOT names that root. From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/infiquetra/infiquetra-agent-plugins/HEAD/plugins/saga/README.md ## Skills - brainstorm: Deep-dive one chosen Infiquetra idea into a right-sized requirements document before planning. - code-review: Run the pre-merge code review as a policy-free executor of the lifecycle repository's lens roster. Reads the lens declaration from the run record, resolves review_roster.v1 with the sdlc's own generator, runs one Lens Reviewer per selected lens, computes the verdict in code from the catalogue's str… - doc-review: Review Infiquetra plans, requirements, and SDLC documents for implementation readiness. - founder-review: CEO/founder-mode scope and ambition review. Rethink the problem, find the 10x product, challenge premises, expand or cut scope deliberately, across four committed modes (SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, SCOPE REDUCTION). Fires upstream of execution on a /plan artifact, STRATEGY.md,… - ideate: Generate and critically evaluate grounded Infiquetra product, architecture, or workflow ideas. Multi-agent divergent→convergent engine: generate many, critique all, explain survivors only. Triggers on "ideate on X", "give me ideas", "what should I improve", "surprise me", "what would you change". - investigate: The Infiquetra systematic-debugging engine. Find the ROOT CAUSE of a bug, test failure, error, or unexpected behavior BEFORE any fix, trace the full trigger→symptom causal chain with no gaps, ground every hypothesis in observed evidence, and only then apply a GATED, trivial-scope, self-verified fix… - office-hours: The two-mode frame-finding front door for early Infiquetra thinking. Startup mode runs the six market/customer forcing questions (stage-aware); Builder mode runs discovery/shaping for infra, workflow, and internal-tooling. Finds the right frame, then routes: to /ideate, /brainstorm, /plan, or /stra… - plan: Create durable Infiquetra implementation plans with issue, review, test, and deploy gates. Interrogates HOW work gets built, writes an agent-consumable plan artifact, records a plan saga, and routes to doc-review and /work. Triggers on "plan this", "how should we build this", "create a plan", "brea… - qa: Run the lifecycle's functional test: the prescribed strategy catalogue. Reads the repository profile and the run record, computes the required strategies from file patterns, lets one advisory judgment widen that set and never narrow it, runs each strategy's driver to passed, failed, or blocked, app… - retro: The Infiquetra lifecycle META-IMPROVEMENT ENGINE. The TERMINAL, ADVISORY lifecycle phase downstream of /qa, it reads the work that shipped, gathers evidence (git forensics behind a stale-base/wrong-today BLOCK guard, saga trajectory, gh issues/PRs READ-ONLY, session transcripts), interviews the ope… - spec: Interrogate a vague ask into a precise, backlog-ready WHAT spec, five-Why, scope/MVP lock, failure-mode enumeration, read-code-first, quantify-everything. Convergent and relentless on one decided direction. Triggers on "spec this out", "turn this into a spec", "what exactly are we building", "sharp… - strategy: Create or maintain the repository root STRATEGY.md: the durable direction anchor (target problem, approach, who it's for, key metrics, tracks). Interview-driven and rerunnable. Triggers on "write our strategy", "update the direction", "what are we working on", "set up the strategy doc", and when /i… - work Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.