product-specification

Plugin product-specification in AI-Foundry-Core/ril-agents. Commands read from the repo's manifest — 1 month ago.

Skills (4)

• acceptance-criteria-patterns

  Given/When/Then format, BDD patterns, quality gates, and definition of done templates. Use when writing acceptance criteria for features, defining quality gates, or specifying what "done" means for a development cycle.

• design-brief-templates

  Design brief structure, interaction specification patterns, and design-engineering handoff formats. Use when translating feature specs into briefs for design teams or documenting design requirements for handoff.

• feature-spec-templates

  Feature specification structure, API contract patterns, and state definition templates. Use when writing implementation-ready feature specs that development agents can execute without ambiguity.

• test-case-design

  Test pyramid structure, boundary analysis, equivalence partitioning, and coverage threshold guidelines. Use when defining what to test and how much coverage to require for a feature.

Slash commands (1)

• /product-specification:run-specification

  Run the Freebird Specification phase — feature specs, acceptance criteria, test case definitions, and design briefs

Subagents (4)

• acceptance-criteria

  Define acceptance criteria, definition of done, and quality gates for features. Produces structured AC documents with testable conditions that gate the handoff from Product to Development. Use PROACTIVELY for acceptance criteria writing, DoD definition, or quality gate specification.

• feature-spec

  Write implementation-ready feature specifications covering UI behavior, backend logic, API contracts, and definition of done. Produces specs precise enough for development agents to implement without human clarification. Use PROACTIVELY for feature specification, technical spec writing, or definitio

• product-design-brief

  Translate feature specs into design briefs for design teams. Produces structured briefs covering user context, interaction requirements, visual direction, and constraints. Use PROACTIVELY for design handoff, design brief creation, or design-engineering alignment.

• product-qa

  Define test cases, coverage requirements, and regression criteria from acceptance criteria and journey maps. Produces test case definitions and coverage requirements that Development agents use to write actual tests. Use PROACTIVELY for test planning, coverage definition, or regression criteria.