design
Product validation gate for RPI pipeline. Validates goal alignment with PRODUCT.md before discovery. Checks: gap alignment, persona fit, competitive differentiation, precedent, scope boundaries. Council-gated with --preset=product. Triggers: "design", "product validation", "validate product fit", "design gate".
Best use case
design is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Product validation gate for RPI pipeline. Validates goal alignment with PRODUCT.md before discovery. Checks: gap alignment, persona fit, competitive differentiation, precedent, scope boundaries. Council-gated with --preset=product. Triggers: "design", "product validation", "validate product fit", "design gate".
Teams using design should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/design/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How design Compares
| Feature / Agent | design | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Product validation gate for RPI pipeline. Validates goal alignment with PRODUCT.md before discovery. Checks: gap alignment, persona fit, competitive differentiation, precedent, scope boundaries. Council-gated with --preset=product. Triggers: "design", "product validation", "validate product fit", "design gate".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# $design -- Product Validation Gate (Codex Native) > **Quick Ref:** Validates that a proposed goal aligns with the product's strategic direction before discovery begins major work. Council-gated with `--preset=product`. --- ## Quick Start ```bash $design "add caching layer for CLI" # validate goal against PRODUCT.md $design --quick "add caching layer" # inline check, no judge spawning $design --strict "redesign hook system" # higher threshold (avg >= 2.5) $design # infers goal from recent context ``` --- ## Execution Steps ### Step 0: Check for PRODUCT.md Locate `PRODUCT.md` in the repo root. ```bash ls PRODUCT.md 2>/dev/null ``` **If absent:** Output a warning and return PASS with note: "No PRODUCT.md found -- skipping product validation gate. Run `$product` to generate one." **If present:** Continue to Step 1. ### Step 1: Load Product Context Read `PRODUCT.md` and extract: - **Mission** -- the product's core purpose - **Personas** -- defined user types and their needs - **Gaps** -- known product gaps or roadmap items - **Competitive landscape** -- how the product differentiates If any section is missing, note it as unavailable and score that dimension conservatively (1). ### Step 2: Score Alignment Matrix Evaluate the proposed goal against five dimensions. Use the scoring rubric in [references/alignment-matrix.md](references/alignment-matrix.md). | Dimension | Score (0-3) | Rationale | |-----------|-------------|-----------| | Gap Alignment | | Does this goal address a known product gap? | | Persona Fit | | Does this serve defined personas? | | Competitive Diff | | Does this strengthen competitive position? | | Precedent | | Has similar work been done before? What can we learn? | | Scope Fit | | Is this appropriately scoped for the current phase? | Compute the average score across all five dimensions. ### Step 3: Run Council Invoke council with the product preset. See [references/product-council-preset.md](references/product-council-preset.md) for judge configuration. ``` Skill(skill="council", args="--preset=product validate design alignment for: <goal>") ``` Pass the alignment matrix from Step 2 as context to the council judges. If `--quick` flag is set, skip council spawning and perform inline assessment instead. ### Step 4: Write Design Artifact Write the design artifact to `.agents/design/`: ```bash mkdir -p .agents/design ``` Filename: `<date>-design-<goal-slug>.md` (e.g., `2026-03-30-design-add-caching-layer.md`) Artifact contents: - Goal statement - Alignment matrix with scores and rationale - Council verdict (or inline assessment if `--quick`) - Final verdict and recommendation ### Step 5: Output Verdict Determine the final verdict based on scores: | Condition | Verdict | |-----------|---------| | Average score >= 2.0 AND no dimension at 0 | **PASS** -- goal aligns with product direction | | Average score >= 1.5 OR one dimension at 0 with others strong | **WARN** -- goal has alignment concerns, review before proceeding | | Average score < 1.5 OR multiple dimensions at 0 | **FAIL** -- goal does not align with product direction | When `--strict` is set, raise the PASS threshold to average >= 2.5. Output the verdict in this format: ``` DESIGN VERDICT: <PASS|WARN|FAIL> Gap Alignment: <score>/3 -- <one-line rationale> Persona Fit: <score>/3 -- <one-line rationale> Competitive Diff: <score>/3 -- <one-line rationale> Precedent: <score>/3 -- <one-line rationale> Scope Fit: <score>/3 -- <one-line rationale> Average: <avg>/3.0 Artifact: .agents/design/<filename>.md ``` --- ## Flags | Flag | Effect | |------|--------| | `--quick` | Inline check without multi-perspective spawning. Faster but less thorough. | | `--strict` | Raise PASS threshold from avg >= 2.0 to avg >= 2.5. Use for high-stakes changes. | --- ## Reference Documents - [references/alignment-matrix.md](references/alignment-matrix.md) -- Scoring rubric for the five alignment dimensions - [references/product-council-preset.md](references/product-council-preset.md) -- Council `--preset=product` judge configuration and verdict rules --- ## See Also - `../council/SKILL.md` -- Multi-model consensus council - `../product/SKILL.md` -- Generate PRODUCT.md - `../discovery/SKILL.md` -- Discovery phase orchestrator - `../pre-mortem/SKILL.md` -- Plan validation gate
Related Skills
vibe
Comprehensive code validation. Runs complexity analysis then multi-model council. Answer: Is this code ready to ship? Triggers: "vibe", "validate code", "check code", "review code", "code quality", "is this ready".
validation
Full validation phase orchestrator. Vibe + post-mortem + retro + forge. Reviews implementation quality, extracts learnings, feeds the knowledge flywheel. Triggers: "validation", "validate", "validate work", "review and learn", "validation phase", "post-implementation review".
update
Reinstall all AgentOps skills globally from the latest source. Triggers: "update skills", "reinstall skills", "sync skills".
trace
Trace design decisions and concepts through session history, handoffs, and git. Triggers: "trace decision", "how did we decide", "where did this come from", "design provenance", "decision history".
test
Test generation, coverage analysis, and TDD workflow. Triggers: "test", "generate tests", "test coverage", "write tests", "tdd", "add tests", "test strategy", "missing tests", "coverage gaps".
status
Single-screen dashboard showing current work, recent validations, flywheel health, and suggested next action. Triggers: "status", "dashboard", "what am I working on", "where was I".
standards
Language-specific coding standards and validation rules. Provides Python, Go, Rust, TypeScript, Shell, YAML, JSON, and Markdown standards. Auto-loaded by $vibe, $implement, $doc, $bug-hunt, $complexity based on file types.
shared
Shared reference documents for multi-agent skills (not directly invocable)
security
Continuous repository security scanning and release gating. Triggers: "security scan", "security audit", "pre-release security", "run scanners", "check vulnerabilities".
security-suite
Composable security suite for binary and prompt-surface assurance, static analysis, dynamic tracing, repo-native redteam scans, contract capture, baseline drift, and policy gating. Triggers: "binary security", "reverse engineer binary", "black-box binary test", "behavioral trace", "baseline diff", "prompt redteam", "security suite".
scenario
Author and manage holdout scenarios for behavioral validation. Scenarios are stored in .agents/holdout/ where implementing agents cannot see them. Triggers: "$scenario", "holdout", "behavioral scenario", "create scenario", "list scenarios".
scaffold
Project scaffolding, component generation, and boilerplate setup. Triggers: "scaffold", "new project", "init project", "create project", "generate component", "setup project", "starter", "boilerplate".