Results for “requirements”

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Displays comprehensive project statistics including phases, plans, requirements, git metrics, and timeline.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling.

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

Use when you have a spec or requirements for a multi-step task, before touching code. Writes comprehensive implementation plans.

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

Esboça a abordagem técnica como delta sobre o legado, gerando roadmap, investigation, data-delta, onboarding e interfaces da feature ativa. Use quando o usuário digitar "/reversa-plan", "reversa-plan", "esboçar plano técnico" ou pedir para virar requirements em desenho de solução. Terceiro skill do ciclo forward, depois de `/reversa-requirements` e (opcionalmente) `/reversa-clarify`.

Run a structured discovery interview and produce a complete, developer-ready Product Requirements Document. Load when the user asks to write a PRD, create product requirements, document a feature, define user stories with acceptance criteria, or turn a rough idea into a formal product requirements document. Also triggers on "document this feature", "write requirements for", "create a one-pager", "turn this into a PRD", "I need a PRD for", or any request to produce a structured product document for stakeholder alignment or engineering handoff. Supports Full PRD, Lean PRD, and One-Pager formats. Note: for executable feature specifications (FRs, NFRs, ACs as Given/When/Then consumable by AI coding agents), route to `feature-spec` instead — PRDs frame the product, feature-specs encode the implementable contract.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Guides collaborative dialogue to turn ideas into fully formed designs and specs before any implementation begins.

Use this skill to maintain a compliant DOT accident register. Covers § 390.15 requirements, what's recorded, retention period.

Use this skill for transporting steel coils. Covers § 393.120 specific rules, chain requirements, dunnage placement, and inspection procedures.

Strategic business analyst and requirements expert. Use when the user asks to talk to Mary or requests the business analyst.

Break requirements into epics and user stories. Use when the user says "create the epics and stories list"

Strategic business analyst and requirements expert. Use when the user asks to talk to Mary or requests the business analyst.

Strategic business analyst and requirements expert. Use when the user asks to talk to Mary or requests the business analyst.

Guides CAPA effectiveness assessment with verification methods, SMART criteria, and closure requirements.

Minimal, pattern-matching code output. Write the least code that satisfies requirements. Match existing project patterns. Use Write/Edit tools only.

Vibe Code Orchestrator (VCO) is a governed runtime entry that freezes requirements, plans XL-first execution, and enforces verification and phase cleanup.

Use before any creative or ambiguous work - new features, new components, or behavior changes - to explore intent, requirements, and design before implementation starts.

Screen products for FDA, EPA, USDA, CPSC, FCC, and other government agency requirements using AskRosetta. Use when checking regulatory compliance for US imports.

Generates personalized proposals for freelance gigs on Upwork, Freelancer, PeoplePerHour, and Guru. References specific project requirements and includes relevant case studies.

Tend the Allium garden. Use when the user wants to write, edit, update, add to, improve, clarify, refine, restructure, fix or migrate Allium specs. Covers adding entities, rules, triggers, surfaces and contracts, fixing syntax or validation errors, renaming or refactoring within specs, migrating specs to a new language version, and translating requirements into well-formed specifications. Pushes back on vague requirements.

Guides a structured brainstorming session that surfaces user ideas, narrows options, and produces a spec file for later planning.

Guides a structured brainstorm that surfaces user ideas, explores directions, and produces a spec and report for later planning.

Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

Generate comprehensive checklists to validate requirements quality (Unit Tests for Specs). Critically examine the spec for clarity, completeness, and consistency before implementation starts.

Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.

Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.

Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.

Verify a GitHub pull request against a Jira issue's goals, requirements, and acceptance criteria, then post a PR comment with the findings. Use when a user asks Codex or MoonMind to compare a PR to a Jira story/task/bug, confirm whether a PR satisfies Jira requirements, audit implementation coverage from Jira, or publish a Jira-vs-PR verification summary.

Create or update a MoonSpec feature specification from a natural language feature request or referenced declarative design. Use when the user asks to run or reproduce `/moonspec.specify`, create a `spec.md`, initialize a feature directory under `specs/`, preserve the original feature request for later verification, map source design requirements, or generate a single-story MoonSpec specification with a requirements quality checklist.

Apply comprehensive Python testing strategies using pytest, including TDD methodology, fixtures, mocking, parametrization, and coverage requirements.