skills.rest
petrSimonidesXart
petrSimonidesXartCOMMUNITY
Explore all skills by this author →
GitHub

validate-artefacts

Validate Discovery artefacts against governance rules and required frontmatter fields.

Updated Mar 8, 2026
Search Tags:#epics#governance#stories#acceptance-criteria#artefact-validation#discovery-delivery
One-click install
npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill validate-artefacts-petrsimonidesxart
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-artefacts
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/discovery/validate-artefacts
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill validate-artefacts-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that Discovery artefacts (Epics, Stories, PRD, marketing, strategy) are clear, governed, complete, and safe to pass into Delivery.

Core Features & Use Cases

  • Enforces outcome-oriented Epics and linked, measurable Stories
  • Checks governance rules across artefacts (PRD, marketing, strategy) and required frontmatter fields
  • Produces a concise Validation Report detailing pass/fail criteria and blockers

Quick Start

Run this skill after Epics and Stories are created to validate governance, clarity, and completeness before Delivery.

Frequently Asked Questions about validate-artefacts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Discovery artefacts before passing them into Delivery?▼

To validate Discovery artefacts before Delivery, run this skill to check that Epics, Stories, PRDs, and strategy documents meet governance rules, contain required frontmatter fields, and include non-empty skills_invoked. It generates a concise Validation Report detailing pass/fail criteria and blockers.

What governance rules apply to Epics and Stories during Discovery?▼

Governance rules for Epics and Stories require outcome-oriented Epics with linked, measurable Stories. Epics must include generate-epics in skills_invoked, Stories must include generate-stories, and every artefact must contain a non-empty skills_invoked frontmatter field to pass validation.

When should I run artefact validation in the Discovery stage?▼

You should run artefact validation in the Discovery stage immediately after Epics and Stories are created. This ensures governance, clarity, and completeness are verified before the artefacts transition into Delivery, preventing blockers and incomplete requirements from advancing.

Can I check if a PRD has the required frontmatter fields for Delivery?▼

Yes, you can check if a PRD has the required frontmatter fields for Delivery by validating that the create-prd skill is included in skills_invoked. The validation process ensures all PRD artefacts are clear, governed, complete, and safe to pass into Delivery.

What happens if an artefact fails validation before Delivery?▼

If an artefact fails validation before Delivery, the process produces a concise Validation Report detailing the specific pass/fail criteria and blockers. This report identifies which governance rules or required frontmatter fields are missing, preventing unclear or incomplete artefacts from passing.

Related Skills

Explore More Product & Management Skills→
petrSimonidesXartpetrSimonidesXart

skill-usage-audit

Audit Epic and Story artefacts for frontmatter governance attestations and compliance.

Community
Intermediate
petrSimonidesXartpetrSimonidesXart

discovery-high-level-plan

Transform vague human intent into a governed discovery plan with validation gates.

Community
Advanced
Fr-e-dFr-e-d
157

validate-artefacts

Validate Epics and Stories against governance rules before Delivery handover.

Community
Intermediate
LeoWSY-hashblueLeoWSY-hashblue
3

source-code-scanning

Scan source code for vulnerabilities, secrets, and dependency CVEs.

Community
Advanced