pdsf

Plugin pdsf from marketplace prompt-driven-software-factory in Loulen/prompt-driven-software-factory. Commands read from the repo's manifest — 9 days ago.

Skills (16)

• agentic-tests

  Runs the project's agentic tests — by default the current ticket's Feature Path (FP), or the full suite of Happy Paths (HP) when "HP"/"all" is requested or when on an integration branch with an open MR. Use when running agentic tests, validating a ticket before auto-merge, or running the HP suite be

• build-factory

  Entry point of the factory. Two modes — scaffold (wire the two backlogs, triage vocabulary, and domain docs, then lay down CLAUDE.md / CONTEXT.md / docs/adr/) and context (bootstrap CONTEXT.md's glossary + foundational ADRs, the project's first grilling). Detects what's already wired and offers the

• clean-context

  Prune the project's accumulated context by the factory : CONTEXT.md, the ADRs, and code comments. A heavy, occasional refactor on its own branch and PR. Use on "clean the context", "prune the docs/ADRs/comments", or when the domain docs have visibly bloated.

• code-review

  Two-axis review of a diff — Standards (does the code follow this repo's documented coding standards and avoid code smells?) and Spec (does the code match what the originating spec/ticket asked for?). Use when a review is needed on a branch, a PR, work-in-progress changes, or "review since X", includ

• codebase-design

  Shared vocabulary for designing deep modules. Use when designing or improving a module's interface, finding deepening opportunities, deciding where a seam goes, making code more testable or AI-navigable, or when another skill (e.g. tdd) needs the deep-module vocabulary.

• domain-modeling

  Actively build and sharpen a project's domain model. Use when a grilling session or another skill is writing or editing CONTEXT.md, recording an ADR, or resolving codebase terminology — not merely reading vocabulary.

• git-flow

  Project git flow (branches, PR/MR, position check before dev). Use when starting or finishing a dev, branching, opening a PR/MR, merging, or to know which branch to work from.

• grill-with-docs

  Per-story grilling that stress-tests your plan against the project's domain model, sharpens terminology, and writes CONTEXT.md/ADRs inline as decisions crystallise. Run it when designing a business user story before slicing it into work.

• grilling

  Grill the user relentlessly about a plan, decision, or idea until you reach shared understanding. Use when a session or another skill needs to stress-test thinking one decision at a time, or on any "grill" trigger phrase.

• implement

  Implement a spec or set of tickets by orchestrating a tdd role, an independent code-review role, and an agentic-tests role in a loop until build, tests, and the Feature Path are green with no blocking finding.

• tdd

  Test-driven development. Use when the user or an orchestrating skill wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants tests at pre-agreed seams.

• to-spec

  Turn the current conversation into a spec and publish it to the technical backlog — no interview, just synthesis of what you've already discussed.

• to-tickets

  Break a plan, spec, or the current conversation into vertical-slice tickets on the technical backlog, each declaring its blocking edges — text in one file per ticket locally, or native blocking links on GitHub/GitLab.

• to-us

  Turns a feature or idea into business User Stories on the business backlog. Runs a senior-PO grilling — the grilling method guided by the existing CONTEXT.md glossary — writes each retained slice to the US template, and publishes backend-agnostically after a mandatory human review. The PO front of t

• triage

  Move issues (and external PRs, where the tracker treats them as a request surface) through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

• verify-factory

  Re-runnable health check for the factory wiring in this repo. Probes both backlogs, triage labels, tooling auth, the agentic driver, the build-factory scaffold and context, that the factory artifacts are versioned (not gitignored), git-flow health, and the US template; reports pass/fail, offers to f