cc-sdlc

Plugin cc-sdlc from marketplace cc-sdlc in zolem/cc-sdlc. Commands read from the repo's manifest — 1 month ago.

Skills (2)

• generate-brief

  Interactive Q&A to generate a structured product brief for the SDLC pipeline

• orchestrate

  Orchestrate the full SDLC pipeline from a product brief

Subagents (13)

• architect

  Produces an implementation plan by combining the curated context briefing with the requirements doc. Reads the target codebase to confirm patterns, then maps each requirement to concrete technical decisions tuned to the project's stack and conventions. Requirements + context in, architecture plan ou

• code-reviewer

  Senior engineering review of the completed implementation. Verifies the code fulfills the architecture document and adheres to engineering best practices — SOLID where applicable, composition over inheritance, and appropriate use of design patterns. Produces findings the task-planner consumes in fix

• context-curator

  Produces a focused, requirement-specific context briefing for downstream SDLC agents. Reads the requirements doc and the target repo's docs and code, then writes a distilled context.md tuned to the surfaces the feature actually touches. Requirements doc in, context briefing out.

• engineer

  Implements a single task from a task file. Reads the task spec, implements all required code across all layers, writes the specified tests, verifies all acceptance criteria and tests pass, and confirms done. Task file in, working code out.

• manual-tester

  Exploratory QA tester with browser access. Starts the app, walks through each user story in a real browser using Claude's built-in Chrome integration, and reports issues that automated tests might miss. Docs folder in, manual test report out.

• merge-resolver

  Resolves git merge conflicts by understanding the intent of both conflicting tasks. Given the conflicting files and the task specs for both sides, synthesizes a correct resolution that satisfies both intents. Conflict + task specs in, clean merge out.

• plan-explainer

  Compiles the full pre-implementation planning bundle (requirements, architecture, test plan, task index, phase files) into a single self-contained HTML brief the engineer reviews and approves before coding starts. Plan docs in, plan.html out. Runs after task-planner.

• product-manager

  Transforms a product brief into a structured requirements document using user story methodology. Given a brief, produces personas, prioritized user stories with acceptance criteria, non-functional requirements, and constraints. Brief in, requirements doc out.

• qa-analyst

  Produces a user-focused test plan from a requirements document. Maps each user story and acceptance criterion to test cases that describe what real users will do, including risky inputs and edge cases a user might actually trigger. Requirements doc in, test plan out.

• qa-verifier

  Verifies the implementation against the test plan. Runs the full test suite, checks that every test case from the test plan has been implemented, and reports pass/fail with details. Docs folder + codebase in, verification report out.

• security-reviewer

  Reviews the implementation for security vulnerabilities. Checks for OWASP Top 10 issues and common security mistakes in the changed code. Reports findings by severity. Codebase in, security report out.

• task-planner

  Decomposes a requirements doc, architecture plan, and test plan into an ordered sequence of implementation phases. Each phase is a cohesive unit of work for a single engineer. Produces individual phase files and a phase index for the orchestrator. Docs folder in, phase files out.

• walkthrough-author

  Generates a per-phase walkthrough document from the phase's atomic commits and planning artifacts. Reads the phase file, architecture, requirements, and stack.json, then narrates each commit as a "stop" telling the reviewer what to look for and why — not what changed. Phase number + docs folder in,

Similar plugins