pi-dev

Plugin pi-dev from marketplace pirras-marketplace in pirras-torres/pirras-marketplace. Commands read from the repo's manifest — 1 month ago.

Skills (21)

• backend-architecture

  Use when creating a backend architecture document. Reads existing project docs to determine what decisions matter for this specific project, then interviews accordingly. Writes to 04_tech/.

• backlog

  Use when creating backlog items (PBIs) for a software project. Requires slice discovery documents to exist. Generates verifiable user stories per slice and writes to 05_scrum/.

• business-rules

  Use when creating a Business Rules document. Starts from invariants already defined in the domain model, then expands with additional rules per subdomain. Writes to 02_business/.

• data-model

  Use when creating a Data Model document. Derives entities from the domain model, then asks about storage details per entity. Writes to 02_business/.

• decision-docs

  Use when documenting an architectural or product decision. Creates an Architecture Decision Record (ADR) capturing context, options, and rationale. Writes to docs/06_decisions/.

• definition-of-done

  Use when creating a Definition of Done for a Scrum team. Reads Product Goal, principles, architecture, and slice risk docs to suggest criteria, then interviews the user to confirm. Writes to 05_scrum/.

• definition-of-ready

  Use when creating a Definition of Ready for a Scrum team. Reads existing architecture and product docs to suggest criteria, then interviews the user to confirm. Writes to 05_scrum/.

• domain-model

  Use when creating the domain model document for a software project. Defines the ubiquitous language, entities, relationships, and business rules. Writes to 02_business/.

• frontend-architecture

  Use when creating a frontend architecture document. Reads existing project docs to determine what decisions matter for this specific project, then interviews accordingly. Writes to 04_tech/.

• guide

  Use when starting, continuing, or resuming work on a software project. Reads project memory and doc state, determines what phase the project is in, and suggests the concrete next action. Run at the start of every session.

• personas

  Use when creating user personas for a software project. Defines who uses the product, their context, goals, and pain points. Writes to 01_product/.

• prd

  Use when creating a Product Requirements Document (PRD) for a new or existing software project. Interviews the user section by section, challenges vague answers in real time as a Product Coach, and writes the document to disk. Trigger when the user wants to define what their product is, what problem

• product-goal

  Use when creating a Product Goal document. Reads existing PRD success indicators as a starting point, then acts as a devil's advocate to stress-test the goal statement, metrics, and minimum acceptable outcome. Writes to docs/01_product/. Trigger when the user wants to define measurable outcomes, suc

• product-journey

  Use when creating a Product Journey document. Maps the user's full experience from first contact through recurring use using industry-standard journey mapping structure: Actor → Stage → Goal → Actions → Touchpoints → Emotions → Pain points → Opportunities. Outputs Slice signals per stage that slice-

• product-principles

  Use when creating Product Principles for a software project. Defines the decision-making rules that guide product choices. Writes to 01_product/.

• risk-docs

  Use when creating a risk register for a software project. Reads existing docs to identify risks, interviews the user, then rates and documents each risk with mitigation. Writes to 06_decisions/.

• slices-discovery

  Use when doing slice discovery before creating backlog items. Supports four slice types: Functional (user-visible feature), Enabler (unblocks other slices), Spike (time-boxed investigation), Foundational (infra/environment setup). Interviews the user to define scope, traceability, dependencies, and

• sprint-planning

  Use when planning a sprint. Reads the backlog for the active slice, checks stories against Definition of Ready, defines Sprint Goal, and writes the sprint plan. Requires backlog and DoR to exist.

• sprint-review

  Use when closing a sprint. Checks stories against Definition of Done, records what was completed, identifies canonical docs that need updating, captures retrospective insights, and prepares the next slice or sprint.

• ui-spec

  Use when creating a UI specification. Documents visual design: components, typography, color system, spacing, layout, and design tokens. Pure UI only — no user flows, task logic, or business rules.

• ux-spec

  Use when creating a UX specification. Documents the user experience screen by screen: what users see, what they can do, what each action triggers, and what happens in edge cases. Pure UX only - no visual design, colors, typography, or component details.

Similar plugins