Pirras Torres
Community@pirras-torres
Pirras Torres provides 21 documentation skills covering the full software product lifecycle: product discovery, domain modeling, architecture decisions, Scrum planning, and UX/UI specification.
Agent Skills by Pirras Torres
Showing 21 vetted skills indexed across 1 GitHub repositories.
pirras-torresguide
Reads project memory and doc state to determine the current phase and suggest the next Scrum documentation action.
pirras-torresproduct-principles
Generates product principles documentation from structured user interviews about trade-off decisions.
pirras-torresfrontend-architecture
Generates a frontend architecture document by scanning project docs and interviewing on relevant decisions.
pirras-torresbusiness-rules
Generates a business rules document from domain model invariants and per-subdomain rules.
pirras-torresbacklog
Generates prioritized product backlog items with acceptance criteria from slice discovery documents.
pirras-torresdecision-docs
Creates Architecture Decision Records capturing context, options, and rationale in Markdown.
pirras-torresdomain-model
Generates a domain model document defining ubiquitous language, entities, relationships, and invariants.
pirras-torresdefinition-of-ready
Generates a Scrum Definition of Ready document from existing project docs and user interviews.
pirras-torressprint-planning
Generates sprint plans by validating backlog stories against Definition of Ready criteria.
pirras-torresdefinition-of-done
Generates a Scrum Definition of Done document by scanning project docs and interviewing the user.
pirras-torresui-spec
Generates a UI specification document covering components, typography, colors, spacing, and design tokens.
pirras-torresrisk-docs
Creates a rated risk register with mitigations by scanning project documentation and interviewing the user.
pirras-torrespersonas
Interviews the user to define product personas and writes them to a Markdown document.
pirras-torresslices-discovery
Interviews users to define and document Scrum slices as discovery markdown files.
pirras-torresproduct-journey
Generates a product journey document mapping user stages, touchpoints, emotions, and slice signals.
pirras-torresproduct-goal
Creates a measurable Product Goal document from PRD success indicators through structured coaching.
pirras-torresbackend-architecture
Generates a backend architecture document by interviewing users on project-relevant technical decisions.
pirras-torresprd
Interviews users section by section to write a Product Requirements Document to docs/01_product/01_prd.md.
pirras-torressprint-review
Closes a sprint by verifying stories against Definition of Done and updating project memory.
pirras-torresdata-model
Generates a data model document with tables, constraints, and indexes derived from a domain model.
pirras-torresux-spec
Generates per-screen UX specification documents through a structured interview covering content, actions, states, and flows.
Frequently Asked Questions About Pirras Torres
FAQPage SchemaWhat tasks can I accomplish with Pirras Torres's skills?▼
You can generate the full documentation set for a software project: PRDs, product goals, personas, product journeys, domain and data models, business rules, frontend/backend architecture, ADRs, risk registers, UI/UX specs, slice discovery, backlogs, Definitions of Ready/Done, and sprint plans and reviews.
Who are these skills designed for?▼
Product managers, Scrum masters, software architects, and UX designers working on structured software projects. Each skill targets a specific role artifact, from product discovery documents in 01_product/ to Scrum artifacts in 05_scrum/ and technical decisions in 04_tech/ and 06_decisions/.
How do the skills work in practice during a project?▼
Start each session with the guide skill, which reads project memory and doc state to suggest the next action. Individual skills then read existing documents, interview you section by section, challenge vague answers, and write structured files to numbered folders like 01_product/, 02_business/, and 05_scrum/.
What prerequisites or dependencies do these skills have?▼
Several skills require earlier artifacts: backlog needs slice discovery documents, sprint-planning requires an existing backlog and Definition of Ready, and definition-of-done reads the Product Goal, principles, architecture, and slice risk docs. The guide skill orchestrates the correct ordering per session.
How do the skills enforce documentation quality?▼
Skills act as interviewers and coaches rather than passive generators: prd challenges vague answers in real time, product-goal plays devil's advocate on metrics and minimum outcomes, and slices-discovery demands verifiable smoke tests, traceability, and dependencies per slice.