sdlc-analysis

Plugin sdlc-analysis from marketplace anthara-marketplace in anthara-ai/anthara-marketplace. Commands read from the repo's manifest — 20 days ago.

Skills (2)

• incubyte-writing-voice

  Incubyte's sentence-level writing rules for anything a reader outside the team will see. Use when drafting or reviewing findings reports, client-facing summaries, engagement updates, proposals, documentation, website copy, case studies, or posts, and use it whenever a draft reads as AI-generated, ov

• plain-technical-voice

  Incubyte's plain technical writing rules for sentences and headings. Short sentences, active voice, simple verb forms, one name for one thing and no idioms. Use when writing client-facing deck text, findings reports, method sheets, caveats or documentation that must be clear on the first read, inclu

Slash commands (2)

• /sdlc-analysis:diagnose

  Extract raw SDLC records, audit the run and say tersely what is missing and why, build the Portfolio Delivery Diagnostic deck from the records, then verify every number in it against the records before handing it over

• /sdlc-analysis:extract

  Extract raw SDLC records from whatever MCP servers are connected into one file per dataset, plus a gaps.md naming everything unobtainable and why

Subagents (8)

• cicd-extractor

  Use this agent to extract raw CI/CD records — pipeline/workflow definitions, runs, jobs and steps, deployments, and re-run/approval events — from whatever CI/CD provider (Azure Pipelines, GitHub Actions, or Jenkins) is connected via MCP or CLI, writing each dataset's records and sidecar directly to

• incidents-extractor

  Use this agent to extract raw incident-management records — services and escalation policies, incidents, incident timeline/log entries, alerts, on-call schedules and shifts, and priority/severity definitions — from whatever incident-management provider (PagerDuty or Opsgenie) is connected via MCP, w

• report-analyst

  Use this agent to turn an audited sdlc-analysis extraction run into a filled Portfolio Delivery Diagnostic deck whose every number is reproducible: it writes a deterministic compute.mjs over the run's records, captures its output as metrics.json, fills the deck template from those metrics only, and

• report-verifier

  Use this agent as the final gate on a filled sdlc-analysis diagnostic deck: it reads the mechanical verifier's output, adjudicates every number the deck shows outside a claim, checks each claim's stated method against what compute.mjs actually does, opens a sample of cited receipts in the records, a

• run-auditor

  Use this agent to audit a finished sdlc-analysis extraction run before any report is built on it: it reads the sidecars, the run manifest, gaps.md and the run validator's output, decides whether the data is READY, DEGRADED or BLOCKED, and renders a terse at-a-glance report naming exactly which data

• scope-scout

  Use this agent to enumerate a run's candidate scope units — repositories (domain a), pipeline definitions (b), boards / projects (c), services (d) — with each unit's provider-native id and last-activity timestamp as the provider's own listing reports it, so the /sdlc-analysis:extract orchestrator ca

• tickets-extractor

  Use this agent to extract raw ticket-tracker records — projects and boards, issues, the issue changelog, sprints, comment counts and links, and the backlog snapshot — from whatever tracker (Jira, Linear or Azure Boards) is connected via MCP or CLI, writing each dataset's records and sidecar directly

• version-control-extractor

  Use this agent to extract raw version-control records — repositories, commits, pull requests, review events, review comments, branches, and tags/releases — from whatever VCS provider (GitHub or Azure DevOps) is connected via MCP or CLI, writing each dataset's records and sidecar directly to disk. It

Similar plugins