dare-to-rise-code-plan

Generates governed multi-stage code plans with hook-enforced quality gates and model-tier assignments.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill dare-to-rise-code-plan-gozonerd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dare-to-rise-code-plan
Source: https://github.com/gozonerd/shadow-ai-assessment/tree/main/.claude/skills/dare-to-rise-code-plan
Command: npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill dare-to-rise-code-plan-gozonerd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Planning a coding task without structure produces inconsistent implementations, skipped testing, and unenforced quality standards. This Skill produces a structured, backwards-planned code plan where every stage boundary is governed by deterministic hooks, ASAE audit gates, and hardwired accessibility and test-coverage requirements. ## Core Features & Use Cases - Prerequisite Document Gating: Requires five approved input documents (PRD, TRD, AVD, TQCD, UXD) before planning begins, with portable prompt generation for authoring missing documents in other LLM sessions. - 20-Track Stage 00 Research: Researches tech stack, standards, benchmarks, security, observability, performance, deployment, accessibility tooling, and more before any plan is written. - Hook-Orchestrated Governance: Enforces Claude Code hooks, git pre-commit/pre-push hooks, ASAE gates, and meta-ASAE verification at every stage boundary so quality checks cannot be silently skipped. - Model-Tier Assignment: Assigns Opus, Sonnet, or Haiku per stage with plan-specification-depth tags (Shallow/Medium/Deep) so each task runs on the appropriate model. - Use Case: A developer starting a new SvelteKit application invokes the skill, which verifies the five prerequisite documents, runs multi-track research, authors a staged plan, and enforces WCAG 2.1 AA compliance and 100% test coverage through commit gates. ## Quick Start Ask the assistant to plan this code task using the dare-to-rise-code-plan skill with my approved PRD, TRD, AVD, TQCD, and UXD documents.

Frequently Asked Questions about dare-to-rise-code-plan

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

FAQPage Schema
How do I create a governed code plan with Claude Code?▼

Invoke the dare-to-rise-code-plan skill with five approved prerequisite documents: PRD, TRD, AVD, TQCD, and UXD. The skill runs Stage 00 research, authors a staged plan, and enforces quality gates through hooks at every stage boundary.

What documents are required before code planning starts?▼

Five documents are required: a Product Requirements Document, Technical Requirements Document, Architecture Vision Document, Testing and Quality Criteria Document, and User Experience Document. If any are missing, the skill offers in-thread authoring, portable prompts, or escalation instead of proceeding.

How are AI models assigned to implementation stages?▼

Stages are assigned model tiers in Stage 01: Opus for planning and auditing, Sonnet for scaffolding and judgment-requiring work, and Haiku for rote transcription of Deep-spec content. PreToolUse hooks enforce these assignments structurally.

Does this planning approach enforce accessibility compliance?▼

Yes, WCAG 2.1 AA compliance is hardwired into every stage that produces UI, not added as a later polish pass. Commit gates run accessibility audits via tools like axe-core and block commits on violations.

What happens if a quality gate fails during execution?▼

ASAE gates reset their convergence counter on CRITICAL, HIGH, or MEDIUM findings under strict severity policy. Git pre-commit hooks block commits when tests fail, coverage drops, or ASAE artifacts are missing or malformed.

When should I not use this planning methodology?▼

Avoid it for trivially simple systems such as single-file scripts with no cross-component boundaries, where the AVD can be skipped with justification. The full governance overhead suits production-grade applications, not quick prototypes.