q-engine

Plugin q-engine from marketplace q-harness in phuquocchamp/q-harness. Commands read from the repo's manifest — 3 days ago.

Skills (5)

• feature

  Take a feature from idea to verified code with the q-engine team (product manager, product owner, architect, engineer, reviewer, verifier), pausing for the user's approval between stages. Each stage writes a file that the next stage reads.

• playwright-cli

  Drive a real browser from the shell with the playwright-cli tool. Use when you need to open a web page, click or fill a form, take a screenshot or snapshot, read console or network output, reproduce a UI bug, or check UI behavior by hand. Requires the @playwright/cli package (playwright-cli on PATH

• reproduce-bug

  Reproduce a web app bug in a real browser and write an evidence report. swe-architect plans the hypotheses, swe-verifier reproduces them with playwright-cli, and the main session compiles the report. Proposes a fix but does not apply it.

• swe-commit

  Commit discipline for git. Use when the user asks to commit, write or fix a commit message, split work into several commits, or prepare changes for a pull request. Stages only related changes, keeps secrets out, and writes messages in the project's convention.

• swe-core

  Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Subagents (8)

• swe-architect

  Solution Architecture agent for analyzing, designing, debating, and stress-testing architectural decisions, implementation approaches, and system design choices. Use when you need to: evaluate a proposed architecture, find flaws in an approach, compare design alternatives, audit separation of concer

• swe-database

  Database engineering specialist for schema design, normalization, query optimization, and data modeling. Use when you need to: design or review a database schema, normalize tables to 1NF/2NF/3NF, model entity relationships (1:1, 1:N, N:N), write or audit migrations, design constraints and triggers,

• swe-debugger

  Debugging specialist for root-cause analysis. Use when a test fails, an error or stack trace appears, or behavior differs from what is expected and the cause is not yet known. Finds the root cause with evidence and applies the smallest fix. For bugs whose cause is already known, use swe-engineer ins

• swe-engineer

  Senior software engineer agent for implementing complex, multi-step coding tasks. Use when writing new features, refactoring, implementing user stories or a design, or fixing bugs whose cause is already known. Prefers surgical changes, surfaces tradeoffs, and defines verifiable success criteria befo

• swe-product-manager

  Product Manager agent that owns the "why" and "what" of the product. Use when you need to: identify or validate a market need, conceptualize a product or feature idea, research and compare competitors, analyze target users and their problems, write or update market research, a feature proposal, a Bu

• swe-product-owner

  Product Owner agent that turns a validated product idea into concrete, buildable requirements for the engineering team. Use when you need to: break a feature or epic into user stories, write acceptance criteria (Given/When/Then), define functional requirements, write or update use cases, order and r

• swe-reviewer

  Expert code review specialist. Proactively reviews a diff for correctness, security, and maintainability. Use immediately after writing or modifying code, or before opening or merging a PR. Reviews the code itself; checking the work against requirements is swe-verifier's job.

• swe-verifier

  Verification agent that checks whether a feature or fix meets its requirements and acceptance criteria, then writes a structured report. Use after implementing a feature, before merging a PR, or when asked to verify, validate, or audit an implementation against requirements. Does not change source c

Similar plugins