Skill UI

Automates creation of acceptance criteria within enterprise workflows, guiding through best practices, generating code and configurations, and validating outputs against standards whenever acceptance criteria creator requests arrive.

This skill enables product owners to manage backlogs and execute sprints effectively. It covers writing user stories, defining acceptance criteria, sprint planning, and velocity tracking. Use it for backlog grooming, story estimation, and prioritizing features within Scrum frameworks.

A guide for pausing and asking targeted questions whenever requirements are vague, ensuring the team locks in objectives, scope, constraints, and acceptance criteria before any implementation begins.

A guide for pausing and asking targeted questions whenever requirements are vague, ensuring the team locks in objectives, scope, constraints, and acceptance criteria before any implementation begins.

This skill guides users through structured workshops to define comprehensive product features from scratch. It adopts dual perspectives (Product Manager and Developer) to gather detailed requirements, user stories, and non-functional needs. The output includes EARS-formatted functional requirements, testable acceptance criteria (Given/When/Then), and detailed implementation checklists, ensuring the feature is complete and ready for development.

This skill specializes in transforming theoretical threat models, risk assessments, and business context into concrete, actionable security requirements. It is essential for writing detailed security user stories, defining robust acceptance criteria, building comprehensive security test cases, and ensuring compliance requirement mapping. Use it when bridging the gap between identifying a vulnerability and specifying how the system must be secured.

Guides teams through writing Mike Cohn‑style user stories with Gherkin acceptance criteria so product needs become actionable, testable development work with shared understanding.

This skill guides the user through a structured process of requirement clarification before any development work begins. It ensures that all key details—including objectives, scope, constraints, and acceptance criteria—are explicitly defined. It prevents costly rework by forcing a pause and systematically identifying 'must-have' missing information.

Generates a complete product feature specification by orchestrating the Prometeo PM agent, covering acceptance criteria, scope, dependencies, risks, and structured handoff notes so teams can confidently implement new work.

This skill enforces a mandatory, structured gate for starting new implementation tasks. It mandates that all work must be tracked via a GitHub issue, requiring explicit, testable acceptance criteria before any execution can begin. It defines a strict workflow (Problem, Goal, Scope, Acceptance Criteria, Status) to manage task readiness, ensuring that development only proceeds when criteria are fully defined and verifiable.

This guide enforces the 'spec-first' principle in software development, treating the specification as a non-negotiable contract. It outlines a rigorous, multi-stage workflow detailing mandatory sections (Functional/Non-Functional Requirements, Acceptance Criteria, API Contracts, Data Models) and bounded autonomy rules. Users learn how to define the system 'must do' before writing a single line of code, thereby minimizing rework and eliminating scope creep.

A comprehensive skill for integrating development workflows directly with Jira. Users can retrieve, analyze, and update Jira tickets, including extracting testable acceptance criteria, transitioning status, adding comments, and searching issues using JQL. Supports both MCP-based and direct REST API interactions.