canon-requirements

Run bounded Canon requirements runs with RISK, ZONE, and authored inputs.

1|Updated Mar 26, 2026

Search Tags:#requirements #prd #ai-assistant #preflight #canon #bounded

Ready to run

npx skills add https://github.com/apply-the/canon --skill canon-requirements

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: canon-requirements
Source: https://github.com/apply-the/canon/tree/main/.agents/skills/canon-requirements
Command: npx skills add https://github.com/apply-the/canon --skill canon-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canon requirements runs require users to memorize or copy raw CLI commands. This skill lets you start a bounded Canon requirements run directly from your AI assistant, removing the need to recall the exact syntax.

Core Features & Use Cases

Orchestrates preflight validation to ensure RISK, ZONE, and inputs are present before invoking Canon.
Guides authored-body creation by prompting and organizing the canonical requirements under canon-input/requirements.
Produces end-to-end PRD artifacts under the Canon-managed tree, enabling a readable product specification.

Quick Start

Ask your AI assistant to start a bounded Canon requirements run by providing RISK, ZONE, and at least one authored input.

Frequently Asked Questions about canon-requirements

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

FAQPage Schema

How do I generate a PRD from my AI assistant without using CLI commands?▼

You can generate a PRD directly from your AI assistant by launching a bounded Canon requirements run. The skill enforces preflight checks and guides you to author the canonical requirements body, storing the resulting product specification artifacts under the .canon tree.

What inputs do I need to start a Canon requirements run?▼

Starting a Canon requirements run requires specifying RISK and ZONE parameters alongside at least one authored input. The skill enforces these preflight validations and organizes your authored inputs under the canon-input/requirements directory before invocation.

How does preflight validation work for bounded Canon requirements runs?▼

Preflight validation checks that RISK, ZONE, and at least one authored input are present before invoking Canon. This ensures the canonical requirements body is properly authored under canon-input/requirements, preventing incomplete runs and missing PRD artifacts.

Where are PRD artifacts stored after a Canon requirements run completes?▼

PRD artifacts from a Canon requirements run are stored under .canon/artifacts/<RUN_ID>/requirements/. The read-end PRD becomes accessible in the .canon tree after the run completes, providing a readable product specification output.

Can I author canonical requirements bodies directly through my AI workflow?▼

Yes, this skill guides authored-body creation by prompting you to organize canonical requirements under canon-input/requirements. It orchestrates the workflow from your AI assistant, removing the need to memorize raw CLI syntax for Canon runs.

What limitations exist when launching bounded Canon requirements runs from an AI assistant?▼

Bounded Canon runs require explicit RISK, ZONE, and authored input parameters to pass preflight checks. Without these mandatory inputs properly organized under canon-input/requirements, the skill cannot invoke Canon or generate the resulting PRD artifact set.