agentic-sdlc

Plugin agentic-sdlc from marketplace agentic-os in kinnister/agentic-os. Commands read from the repo's manifest — 13 days ago.

Skills (27)

• acceptance-check

  Required functional proof for anything user-visible, run right after gate-runner. When a change touches UI or another externally visible surface, it reuses e2e coverage that already exists, or generates a focused Playwright check when none does; either way it captures screenshots, console output, an

• code-review-orchestrator

  Resolves the SDLC code-review gate with a multi-lens review fan-out and persists one canonical verdict JSON as the hand-off back to gate-arbiter. Invoked inline (Skill tool) by gate-arbiter at gate ids `code-review.final` (full multi-lens pass after implementation evidence) and `code-review.check` (

• code-review

  Standalone, on-demand multi-lens code review of local git changes, outside any managed SDLC pipeline. Invoke when the user says "code review", "review my changes", "review my code", "review my branch", "review staged changes", "review this diff", or "run a code review" — and no pipeline is already d

• effort-sizing

  Thin gating skill that classifies a task's complexity when the caller's own heuristics cannot confidently route it. Invoke when you need to decide between going straight to detailed planning versus running a design/ideation pass first, or when a task might be too large to plan directly. Trigger phra

• gate-arbiter

  Invoke this skill whenever an SDLC pipeline phase reaches a judgment gate and needs a resolved, logged verdict — spec approval, plan approval, QA drift, code review (final or check round), requirements ambiguity, spec clarification, or feature verification. Trigger phrases include "resolve this gate

• gate-runner

  Run the host project's quality gates in a fixed order (lint -> build -> unit tests -> affected tests -> optional UI tests) and return a structured, machine-readable merge-readiness report. Runner-agnostic: detects the build tool (npm/pnpm/yarn/cargo/poetry/uv/go) from manifest files, caches a gate p

• mr-submit

  Commit with a mandatory ticket reference, push, and open an MR or PR. Commit, branch, and title conventions are read from `.agentic/guides/standards/git-workflow.md`; the MR/PR adapter (a CLI, MCP server, or custom command) is read from the `## Review Adapter` section of `.agentic/guides/project.md`

• mr-watch

  Watch one open MR/PR and autonomously clear whatever blocks merge — CI failures, requested-change reviewer comments, and merge conflicts — on a polling loop until the request merges, closes, or the user stops it. Adapter-driven: no source-control platform is hardcoded. Invoke when the user says "wat

• qa-baseline

  Bootstrap the QA knowledge foundation for a repo: discover test files, coverage reports, CI test gates, and QA docs; configure adapters to external QA sources (test-case management, QA documentation, external test repos); then write two persistent guides — qa-strategy.md and qa-health.md — under .ag

• qa-case-generator

  Turn one work-item id into reviewed, backend-synced functional test cases. Invoke when the user says "generate test cases for PROJ-123", "write test cases from this ticket", "qa cases for <ticket>", or hands you a single Jira / Azure DevOps / GitHub / GitLab work-item id and wants manual or API-leve

• qa-e2e-generator

  Turn one work-item id into executable end-to-end (UI/API) test automation. Invoke when a QA engineer hands you a ticket id and wants a full E2E suite generated, run, reviewed, and pushed for review. Triggers: "generate e2e tests for PROJ-123", "qa-e2e-generator PROJ-123", "write end-to-end tests for

• qa-scoping

  Plans and reviews QA on a per-feature basis, in three modes that sdlc-engine invokes directly: --checklist (Phase 6) turns requirements and QA knowledge into qa-checklist.md before implementation starts; --review-tests (Phase 8) reviews the tests that were written for quality and completeness; --upd

• release-manager

  Audit a software release by cross-referencing git commits in a release range against tickets carrying the release's fix version, then emit a gap-analysis report in Markdown tables. Invoke when the user says "validate the release", "release audit", "check what shipped in <version>", "cross-reference

• repo-audit-guides

  Read-only audit of a repository's documentation, structure, and agentic assistant setup, run before knowledge planting so the downstream repo-guides workflow knows how to handle every pre-existing doc and assistant surface. Invoke when the user asks to survey, audit, inspect, assess, or review repo

• repo-guides

  First-time knowledge setup for a repository: survey the stack, generate the curated guide tree under .agentic/guides/, and wire the AI entrypoint (AGENTS.md plus a CLAUDE.md shim). User-triggered only. Invoke when the user says "repo guides", "set up repo guides", "generate the guides", "bootstrap t

• role-memory

  Per-role persistent memory for agents — durable curated facts, preferences, and decisions plus an append-only episodic daily log, stored as plain markdown under `.agents/memory/<role>/`. Invoke when the user says "remember this", says "log this", or asks "what did you learn yesterday" — and whenever

• sdlc-auto

  Start an autonomous ("factory mode") SDLC run from a task description, external work-item reference, story path, or greenfield idea, on hosts that support skills but not custom slash commands. Trigger on "run autonomously", "factory mode", "ship this without asking", or a request for the legacy `sdl

• sdlc-brief

  Runs a lightweight, human-in-the-loop SDLC flow for a task the user has already sized as XS/S/M: brainstorm-lite, spec, plan, inline TDD, one code-review round, and gate-runner on the current feature branch — no complexity scoring, no per-task subagents, no evidence files, no worktrees. Invoke on ph

• sdlc-direct

  Lightest-ceremony entry point into the agentic-sdlc pipeline for a task the user has already judged small and unambiguous. Invoke on phrases like "just do this quickly", "small fix, skip the ceremony", "simple task, no spec needed", or "run sdlc-direct on <task>". Runs a mandatory research pass via

• sdlc-engine

  Heavy orchestrator that runs the full 13-stage (Phase 0-12) governed SDLC flow for a single unit of work. Invoke this skill only as the execution engine dispatched by sdlc-guided (mode=hitl) or sdlc-auto (mode=autonomous) — never in direct response to a bare user request, and never with a mode other

• sdlc-guided

  Starts a human-in-the-loop agentic-sdlc run from a task description, an external work-item reference, or a greenfield idea. Triggers include "start sdlc", "implement this with sdlc", "begin SDLC workflow", or a request for the legacy sdlc:start command on a skills-based host. Not for: autonomous run

• sdlc-preflight

  Force-runs a full environment-readiness check for the agentic-sdlc plugin and overwrites .agentic/agentic-sdlc/doctor.json with the fresh result, ignoring any existing fingerprint or TTL cache. Invoke when the user asks to verify the agentic-sdlc setup, re-run doctor, check whether superpowers/node/

• sdlc-runs

  Read-only inspector and resumer for agentic-sdlc heavy-pipeline runs kept under docs/superpowers/runs/. Invoke when the user asks what a run's status is, wants to list or drill into past pipeline runs, needs to pick back up an interrupted run, or is on a skill-only host (for example, Codex) that has

• story-author

  Turn a raw feature idea, improvement, or bug description into a structured user story with testable acceptance criteria, persisted as a local markdown file. Invoke when the user wants to create, draft, or refine a story, ticket, requirement, or acceptance criteria — trigger phrases include "create a

• story-intake

  Normalize a single starting input — free-form text, an external ticket id or URL, a local story path, a local work-item path, or a greenfield idea — into one canonical requirements.md that every later pipeline phase reads, and guarantee a work-item reference exists before those requirements are writ

• telemetry-export

  Project a pipeline run's governance ledgers (events.jsonl, decisions.jsonl) into redacted NDJSON and hand them to a host-declared observability backend. Invoke when an operator wants run/gate telemetry visible outside the workspace — "export run telemetry", "send this run's events to Axiom", "wire u

• test-heal

  Repairs failing tests whose failure is the test's own fault — and only those. Consumes a failure triage (test_issue | environment_issue | flaky | application_issue), fixes test code, fixtures, selectors, and waits, never application code, and never re-runs the suite itself: it applies fixes, sanity-

Subagents (5)

• codebase-scout

  Dispatch codebase-scout before any complexity scoring or brainstorming phase runs, whenever the pipeline needs grounded, read-only facts about the existing codebase rather than assumptions. It never plans or writes implementation code — its only output is a single technical-analysis.md research arti

• guide-sync

  Use this agent when a feature branch has introduced structural or architectural changes and the guide corpus under .agentic/guides/ needs to be checked for drift. It is the standard dispatch target for mr-watch immediately after a merge lands, and repo-guides also points to it whenever ongoing sync

• lead-proxy

  Dispatch this agent whenever the gate-arbiter needs an autonomous stand-in tech-lead judgment at one of the three gates it owns: spec.approved, plan.approved, or qa.drift. It runs after the router's own deterministic pre-checks (evidence-file shape, per-task test-first declaration format) have alrea

• sizing-analyst

  Dispatch this agent whenever a task's size is not obvious from cheap heuristics and the orchestrator needs a defensible, six-dimension complexity score plus a routing call (plan directly vs. brainstorm first vs. split before planning). It never designs or writes code — it reads what earlier phases a

• story-proxy

  Use this agent when gate-arbiter dispatches a requirements.ambiguous or spec.clarification judgment gate during an autonomous SDLC run and no human is available to answer synchronously. story-proxy resolves the open question by applying a fixed, priority-ordered rule set against the original task, s

Hooks (4)

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" sdlc-stage-guard

• Stop

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" ticket-sync

• SubagentStop

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" ticket-sync

• SubagentStop

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" usage-sampler

Similar plugins