software-factory

Plugin software-factory from marketplace software-factory-marketplace in achisolomon/open-software-factory. Commands read from the repo's manifest — 2 days ago.

Skills (8)

• factory-init

  Set up the current repository for the Software Factory agent team — create the docs/ scaffold, capture project facts, and (for existing code) map the repo and derive coding standards. Run once per project.

• frontend-testing

  Plan, write, debug, and verify browser tests for web UI changes using the existing Test Automation Engineer. Use for page or component behavior, responsive layouts, keyboard accessibility, and browser failures; skip for backend-only work and ordinary unit tests.

• health

  Read-only health check of a Software Factory project. Flags stale in-flight dispatches, dead background processes, worktrees with uncommitted or unpushed work, board drift and errors in logs. Use when the user asks for a factory health check, or before a long run or a cleanup.

• resume

  Resume the Software Factory Team Lead after a context compaction or a session restart. Reconciles every in-flight dispatch against the reports on disk before any new work is sent.

• review

  Run a full team review of the current changes, a branch, a task or the whole codebase — architecture and clean-code review, security review, test verification, and cost review when infrastructure changed — and consolidate one verdict.

• session-setup

  Configure the project's Claude Code settings for Software Factory runs. Sets the auto-compact threshold and an allowlist of exact read-only and stack commands, after showing the diff and asking. Claude Code only.

• status

  Show the Software Factory Team table now - who is running, blocked, done since the last status, and what is next. Read-only. Use when the user asks for the status, the team table, or what the team is doing.

• team-lead

  Use when the user says "team lead" or "team leader", addresses the team lead, or asks the team or factory to build, fix, review or report status. The current session becomes the Software Factory Team Lead and drives the specialist agents, stopping at the approval gates.

Subagents (13)

• devops-engineer

  DevOps Engineer of the Software Factory. Use it to plan environments and the deployment model during design review, and to build containers, CI/CD pipelines, infrastructure as code, observability (logs, metrics, traces, alerts), runbooks and release automation. Validates with plans and dry runs only

• exploratory-qa-engineer

  Exploratory QA Engineer (black-box bug hunter) of the Software Factory. Use it at epic end, or when the user asks, to use the running product the way a user would, put data into odd states on a local stack, and prove each bug with a failing repro test. Not a per-task reviewer. Works on local or disp

• finops-engineer

  FinOps Engineer of the Software Factory. Use it to estimate the cost of an architecture before it is built, set cost guardrails, review tasks and infrastructure-as-code plans that add or change paid resources or third-party APIs, check CI workflow changes and the GitHub Actions budget (minutes, larg

• performance-engineer

  Performance Engineer (load tester and sizing expert) of the Software Factory. Use it to review the architecture and code for what breaks under load (missing indexes, N+1 queries, lock ordering and deadlocks, unbounded queries and fan-out, pool and queue limits, synchronous work on hot paths), to siz

• product-manager

  Product Manager of the Software Factory. Use it to turn an idea, feature request or problem into a product vision, a PRD with measurable success metrics and non-functional requirements, and a prioritized backlog of epics and user stories with testable acceptance criteria; and at release time to veri

• project-manager

  Project Manager of the Software Factory. Keeps the GitHub issues and the GitHub Project board in step with the work. Use it to set up the board, to open the issues that are missing (stories, tasks, findings, follow-ups), to move each issue's Status and post its comments as work is dispatched, review

• security-engineer

  Security Engineer of the Software Factory. Use it to threat-model the architecture and set security requirements during design review, to review task diffs, new dependencies and infrastructure-as-code for vulnerabilities, to run read-only security scans (SAST, dependency, secrets, container, IaC), a

• software-architect

  Senior software architect and code reviewer for any project. Use it (1) to map an existing repo or system into Mermaid diagrams, (2) to produce or update the system design — application structure, data flow, component interactions and deployment model — and (3) to review code, pull requests or a who

• software-developer

  Software Developer of the Software Factory. Use it to implement one task from docs/architecture/tasks.md at a time — application code plus its unit tests, following the architecture, ADR rules and coding standards — and to fix findings from architecture, security, test and cost reviews. Works on a l

• team-lead

  Team Lead and orchestrator of the Software Factory agent team. Runs as the main session (claude --agent software-factory:team-lead, or via /software-factory:build). Takes a product idea, feature or fix, drives it through discovery, architecture, build, review and release by classifying each request

• test-automation-engineer

  Test Automation Engineer of the Software Factory, and the team's devil's advocate. Use it to write the test strategy from the PRD and architecture, build and maintain the test framework, write integration, contract and end-to-end tests, verify each task against its acceptance criteria, hunt for the

• triage-classifier

  Triage Classifier of the Software Factory. Use it first on every new request the Team Lead receives (except a plain status question) to classify the work - type, size, the lifecycle path, which conditional reviewers are needed, and whether it is clear enough to start - so small work exits early and

• ux-ui-designer

  UX/UI Designer of the Software Factory. Use it to turn PRD stories into user flows, screen-by-screen wireframe descriptions and a design-tokens system during Discovery and design review, to review the Architect's design and each Build-loop task's UI diff for usability and accessibility, and to hold

Hooks (10)

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/require_agent_model.py"

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/project_bounds.py"

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/gate.py"

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/no_wait.py"

• SubagentStop

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/check_reply.py"

• SessionStart

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/version_check.py"

• SessionStart

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/scratch.py" start

• SessionStart

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/after_compact.py"

• SessionEnd

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/scratch.py" end

• UserPromptSubmit

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/team_lead_trigger.py"

Similar plugins