Dark Factory Lite

Plugin dark-factory-lite from marketplace dark-factory in ruslantrachuk/dark-factory. Commands read from the repo's manifest — yesterday.

Skills (6)

• build-tdd

  Use when the next step is to write the code of a planned piece of work — "build slice 1.1", "implement this task", "build 3.2 from tasks.md", a bd subtask with FILES and TESTS — and as the rules of the feature pipeline's implementers. Builds it by TDD (a failing test first, then the code, then the r

• integrate

  Use when built code is about to be committed — "commit it", "commit this slice", "run the gates", after each build-tdd slice — and as the rules of the feature pipeline's single writer. Runs the slice's tests and lint before the commit, one commit per slice, closes the bd subtask; after the last slic

• plan

  Plan an approved phase before its code: cut it into end-to-end slices, each with its files, test plan, acceptance and dependencies, ready to become bd subtasks. Use when an OpenSpec phase, a ready spec or a bd task is approved and the code is about to start ("plan the phase", "break this into tasks"

• size-task

  Use when a request starts new work in a repository — "add", "build", "fix", "make", "change", "implement", "where do we start", a new ask from the owner or a customer — before any code, spec or branch, even when the answer seems obvious. Sizes the work (trivial / small / large) for the owner's ok an

• wrap

  Wrap up a built, green branch: a note on the bd task, the project documents brought in line, the phase ticked in tasks.md and the PR description in its three sections. Use when the code of a feature or phase is done and reviewed ("wrap up", "write the PR description"), and as the rules of the featur

• wsjf

  The WSJF priority formula and its 1-2-3-5-8-13-20 scales, with who scores each component. Use when scoring or ranking a task or a queue ("WSJF", "prioritise", "business value vs job size"), and as the single source the product-owner and tech-lead roles and the feature-sanity-check skill refer to.

Subagents (4)

• builder

  Builds and integrates planned work in a branch — one slice by TDD (build-tdd), its commit, gates and bd close (integrate), the wrap-up and PR description (wrap). The feature pipeline calls it for its implementers, integrators, Fix and wrap-up steps; by hand it takes a planned bd subtask end to end (

• product-owner

  Judges a task or feature from the product side: is the pain real and where does it come from, does it match the product direction, what changes for the user if it is done and what is missed if not, is every user-facing surface decided. Writes the user flow and WHEN/THEN acceptance scenarios, and sco

• reviewer

  Fresh-context, read-only reviewer of a diff, branch or document through one lens at a time (test pyramid, project invariants, simplification, correctness, screens against the design frames, or the lens you name). Reports findings in the project's review contract format with evidence and severity, an

• tech-lead

  Sizes and shapes technical work and judges technical soundness. Call it by hand to size a task (trivial, small or large) and get a branch, slug and end-to-end phases, to propose how to split a large change, to assess feasibility, reliability and risk of an idea, to score job size (JS) for WSJF, or t

Similar plugins