marsai-dev

Plugin marsai-dev from marketplace marsai in V4-Company/v4-dev-workflow. Commands read from the repo's manifest — 1 month ago.

Skills (11)

• code-review

  Reviews a branch diff on two axes: Standards (does the code follow the team's standards and the repository's?) and Spec (does it do what the ticket asked?). The reviewer fixes and commits what violates the standards and reports what needs a decision. Use when an implementation is finished, before op

• demo

  Builds a working demo of a feature inside the real codebase, on a demo branch, so a real user can use it before any hardening. Use after a grill, when a feature has to prove its value before the technical plan, or when someone asks to see the whole idea working.

• dev-start

  Session entry point for someone who develops: asks once what the person wants to do and takes them to the right skill in the flow. Use when someone is about to start dev work without saying at which stage.

• implement-spec

  Implements a whole spec: walks the slices of the parent issue in blocker order, with one implementer per slice, and delivers one reviewed PR per repository. Use when a parent issue with slices exists and someone asks to implement the spec, the whole feature or all the slices. For a single slice or a

• implement

  Implements a single slice or a small change: dispatches the right implementer, verifies the repository's checks, closes with the review and updates the issue in Linear. Use for an isolated ticket, an adjustment or a bug, whenever the work is writing or changing production code, before writing the fi

• pm-start

  Session entry point for someone who looks after product: asks once what the person wants to do and takes them to the right skill, from the idea to the spec in Linear. Use when a PM is about to start work without saying at which stage.

• prototype

  Builds a throwaway prototype to answer a design question. Use when someone wants to feel whether a business rule or a state machine is right, compare options for a screen, or see what happens in an exchange of events between services when something goes wrong.

• refinement-doc

  Produces the technical refinement document of a ticket or feature as an HTML page in a standard structure (before × after, closed decisions, flow, entity-relationship, contracts, changes per repository, edge cases, rollout, rollback and verification), with the same visual semantics for new × existin

• tdd

  Test-first reference: what a good test is, where it lives and the rules of the red and green cycle. Use when implementing a feature or fixing a bug, and when someone mentions TDD, red-green or integration tests.

• to-spec

  Turns what has already been decided into a spec published on the Linear parent issue, anchored in the current code. After a demo, it cuts the v1 from it. Use after a demo that proved its value, after a grill when the only open doubt is how to build, or when there is a call transcript with decisions,

• to-tickets

  Cuts a spec into vertical slices in Linear, each with the repositories it touches and the blockers between them. Use after to-spec, or when someone asks to break an issue or a plan into tasks.

Slash commands (2)

• /marsai-dev:backend

  Dispatches the TypeScript backend implementer directly, without the routing of implement.

• /marsai-dev:frontend

  Dispatches the React/Next.js frontend implementer directly, without the routing of implement.

Subagents (3)

• backend-engineer-typescript

  Backend implementer for TypeScript services. Makes one ticket work in one repository, test-first, following the examples the repository already has.

• code-reviewer

  Reviewer for a branch diff. Applies the coding standards it is given, fixes what departs from them, commits the fixes, and reports what needs a human decision.

• frontend-engineer

  Frontend implementer for React and Next.js applications (App Router, Server Components). Makes one ticket work in one repository, with the components the repository already has.

Similar plugins