
Functional mythological compression for OCTAVE documents. Semantic shorthand for LLM audiences, not prose decoration
Workflow for transforming prose into semantic OCTAVE structures. Covers tier selection, transformation phases, loss accounting, and decision rules. REQUIRES octave-literacy.
LLM-native structured communication format. Teaches OCTAVE syntax rules, canonical forms, and warning prevention for zero-error .oct.md authoring.
Advanced semantic vocabulary, holographic contracts, and structural patterns for OCTAVE. REQUIRES octave-literacy. Extends literacy with mythology, archetype annotation, v6 contracts, and anti-pattern rules.
Ultra-high density compression using mythological atoms and semantic shorthand. Preserves soul and constraints at 60% compression for identity transmission, binding protocols, and extreme token scarcity.
===SKILL:GAP_OWNERSHIP=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Framework for managing and assigning ownership of cross-boundary gaps" §1::FRAMEWORK GAP_OWNERSHIP_FRAMEWORK::[ DEFAULT_OWNERSHIP::"All unassigned cross-boundary gaps default to holistic-orchestrator", RETAINED_ACCOUNTABILITY::"Delegation transfers execution, not ultimate accountability", ESCALATION_AUTHORITY::"Can reassign ownership based on capability gaps", SYSTEM_STANDARD_BOUNDS::"Cannot abandon accountabilit
Wind/Wall/Door multi-perspective debate orchestration using debate-hall-mcp tools. Use when facilitating structured debates, architectural decisions, or multi-perspective analysis.
===SKILL:CODEBASE_SYNTHESIS=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Methodology for extracting patterns from large-scale file sets" §1::SYNTHESIS_PROTOCOL STEPS::[ SCOPE_DEFINITION::"Clarify exact pattern/cause/decision being investigated", STRATEGIC_SAMPLING::"Identify representative files using Glob patterns", PATTERN_EXTRACTION::"Read targeted files, extract relevant code sections", EVIDENCE_AGGREGATION::"Collect citations: file:line_range, snippet", SYNTHESIS::"Compres
===SKILL:CODE_QUALITY_STANDARDS=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Multi-dimensional quality standards for code assessment" §1::SECURITY VULNERABILITIES::[INJECTION,XSS,CSRF,AUTH_BYPASS,INSECURE_DESERIALIZATION] VALIDATION::[INPUT_SANITIZATION,OUTPUT_ENCODING,PARAMETERIZED_QUERIES] DEPENDENCIES::[OUTDATED_PACKAGES,KNOWN_CVES,SUPPLY_CHAIN_RISKS] §2::ARCHITECTURE PRINCIPLES::[SOLID,DRY,SEPARATION_OF_CONCERNS,MODULARITY] PATTERNS::[DESIGN_PATTERNS,ANTI_PATTERNS,CODE_SMELLS] STRUC
===SKILL:CI_ERROR_RESOLUTION=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Protocol for systematic CI pipeline failure resolution" §1::RESOLUTION_PROTOCOL PHASES::[ LOCAL_VALIDATION::"Ensure 'npm run {audit,lint,typecheck,test,build}' all pass locally first", BRANCH_STRATEGY::"Create 'fix/ci-errors-{timestamp}' branch for isolation", ITERATION_LOOP::"Check CI status -> Fetch logs -> Analyze -> Fix -> Commit -> Push -> Wait", VERIFICATION::"Confirm all checks pass via 'gh pr checks
===SKILL:BLUEPRINT_REFINEMENT=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Methodology for transforming concepts into implementation-ready blueprints" §1::REFINEMENT_PROTOCOL STEPS::[ DECONSTRUCT::"Break breakthrough concept into component interactions", DEFINE::"Specify interface contracts and data models", VALIDATE::"Check technical feasibility with Validator", ALIGN::"Ensure stakeholder consensus with artifacts", PACKAGE::"Create master blueprint for B0 handoff" ] §2::QUALI
===BACKWARD_COMPATIBILITY_VALIDATION=== META: TYPE::SKILL VERSION::"1.0.0" STATUS::ACTIVE PURPOSE::"Interface change impact analysis, breaking change detection, and migration path enforcement" §1::CORE AUTHORITY::BLOCKING[breaking_changes_without_migration_path⊕undocumented_removals] SCOPE::breaking_change_detection⊕consumer_impact⊕semver_alignment⊕migration_requirements MISSION::"Prevent unintended breaking changes and ensure consumers have viable migration paths" §2::PROTOCOL BREAKI
===ABSTRACTION_LAYER_MAPPING=== META: TYPE::SKILL VERSION::"1.0.0" STATUS::ACTIVE PURPOSE::"Layer count analysis, justification framework, and consolidation patterns" §1::CORE AUTHORITY::BLOCKING[unjustified_layers⊕layer_count_violations] SCOPE::layer_inventory⊕justification_per_layer⊕consolidation_recommendations⊕anti_pattern_detection PRINCIPLE::"Every layer must justify its existence — unjustified layers are accumulative complexity" §2::PROTOCOL LAYER_INVENTORY::[ 1::trace_request
Comprehensive catalog of build anti-patterns that degrade quality, increase maintenance, and introduce bugs. Includes detection frameworks and prevention strategies.
===SKILL:BUILD_EXECUTION=== META: TYPE::SKILL VERSION::"3.0" PURPOSE::"Orchestration skill for build execution, delegating to specialized skills and patterns" §1::PHILOSOPHY_DELEGATION BUILD_PHILOSOPHY::"See build-philosophy skill for comprehensive framework" CORE_REFERENCES::[ "build-philosophy: System awareness, MIP, UNDERSTAND→SHAPE→ACT framework", "build-anti-patterns: 9-pattern catalog with detection and prevention", "mip-build: Minimal Intervention for code complexity" ] §2::
===SKILL:CREATIVE_FOUNDATION=== META: TYPE::SKILL VERSION::"2.0" STATUS::ACTIVE PURPOSE::"Methodology for generating breakthrough possibilities through constraint transformation and divergent exploration" §1::CORE MISSION::"Generate multiple distinct alternatives before convergence through constraint-aware creativity" AUTHORITY::"Any agent loading this skill commits to divergent exploration before convergence" PRINCIPLES::[ VISION_WITHIN_CONSTRAINT::"Explore possibility space WITHIN b
===DEPENDENCY_GRAPH_ANALYSIS=== META: TYPE::SKILL VERSION::"1.0.0" STATUS::ACTIVE PURPOSE::"Dependency chain analysis, cycle detection, and coupling metrics" §1::CORE AUTHORITY::BLOCKING[direct_cycles⊕package_cycles]⊕ADVISORY[transitive_cycles⊕coupling_metrics⊕dependency_direction] SCOPE::dependency_mapping⊕cycle_detection⊕coupling_measurement⊕direction_enforcement PRINCIPLE::"Depend toward stability — unstable modules must not be depended upon by stable ones" §2::PROTOCOL MAPPING_PROC
===SKILL:DRIFT_DETECTION=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Early warning system for requirements and process drift" §1::REQUIREMENTS_DRIFT SIGNALS::[ FEATURE_ADDITION_WITHOUT_NORTH_STAR_REFERENCE::{INDICATOR:"New functionality proposed without traceability", RESPONSE:"North Star validation demand"}, SCOPE_BOUNDARY_BLUR::{INDICATOR:"Adjacent problems being solved without approval", RESPONSE:"Boundary enforcement"}, COMPLEXITY_INCREASE::{INDICATOR:"Architecture growing bey
===SKILL:ERROR_TRIAGE=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Systematic error resolution preventing cascade failures" §1::PRIORITY_MATRIX LAYERS::[ 1_BUILD::"Compilation/Syntax/Import errors (Must fix first)", 2_TYPES::"Type mismatches/Interface violations (Cascades)", 3_UNUSED::"Unused vars/imports (Noise reduction)", 4_ASYNC::"Async/Await issues (Architectural)", 5_LOGIC::"Nullish/Truthiness checks (Consistency)", 6_TESTS::"Unit/Integration failures (Fix last)" ] §2:
Strategic oversight mode for the Holistic Orchestrator. Episodic State Machine pattern with ho-liaison advisory (via pal_clink), run_debate escalation, and oa-router delegation. REPLACES holistic-orchestration when loaded.
MCP tool implementation patterns for HestAI including tool structure, session tools, and shared utilities
Functional mythological compression for OCTAVE documents. Semantic shorthand for LLM audiences, not prose decoration
===SKILL:OPTIMIZATION_FOUNDATION=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Methodology for edge-focused discovery and optimization" §1::DISCOVERY_METHODOLOGY STEPS::[ STEP_1::"Map solution boundaries - identify edges and transition zones", STEP_2::"Hunt periphery - explore overlooked areas and rare pathways", STEP_3::"Detect brilliance - find hidden patterns and elegant opportunities", STEP_4::"Verify improvements - benchmark before/after with artifacts", STEP_5::"Deliver br
===SKILL:PRODUCTION_READINESS=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Production readiness validation and domain accountability for critical systems" §1::VALIDATION_FRAMEWORK CRITICAL_LENSES::WILL_IT_BREAK×WILL_IT_SCALE×WHO_MAINTAINS×WHAT_ATTACKS×WHY_COMPLEX WILL_IT_BREAK::[single_points_of_failure, edge_cases, race_conditions] WILL_IT_SCALE::[10x_load_capacity, bottleneck_identification, resource_limits] WHO_MAINTAINS::[3am_debuggability, documentation, operational_runbooks]
===SKILL:PROPHETIC_LENSES=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Methodology for predicting long-term system health and scalability" §1::LENS_FRAMEWORK LENSES::[ WILL_IT_DECAY::"Test integrity trends, architectural erosion, operational complexity", WILL_IT_SCALE::"Pattern support for 10x growth, performance linearity", WHO_MAINTAINS::"Onboarding friction, incident trends, knowledge distribution", WHAT_PATTERNS_EMERGE::"Recurring incidents, hot spots, blast radius expansion"
===SKILL:RAPH_REASONING=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Sequential reasoning and quantified receipts protocol: READ → ABSORB → PERCEIVE → HARMONISE" §1::PROTOCOL PHASES::[ 1_READ::[ GOAL::"Extract facts without interpretation", RECEIPT::"✓ READ complete: {n facts found}" ], 2_ABSORB::[ GOAL::"Identify relationships and dependencies", RECEIPT::"✓ ABSORB complete: {A relates to B}" ], 3_PERCEIVE::[ GOAL::"Map to patterns and frameworks", RECEI
Root Cause, Corrective Action, and Future Proofing - incident management protocol for multi-agent AI systems. Triggers on incidents, system failures, constraint violations, LLM overreach, or post-mortem analysis.
===SKILL:RCCAFP=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Root Cause, Corrective Action, and Future Proofing incident management protocol" §1::PROTOCOL_OVERVIEW RCCAFP::[ FULL_NAME::"Root Cause, Corrective Action, and Future Proofing", ORIGIN::"Daedalus-era LLM Overreach incident (2025-05-26)", SCOPE::"Incident management for multi-agent AI systems with human orchestration oversight", PRINCIPLES::[ "Systematic evidence collection with exact causality chains", "Multi-ag
===SKILL:REGISTRY_PROTOCOL=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Protocol for official architectural change approval" §1::APPROVAL_WORKFLOW PROTOCOL::[ HOOK_BLOCK_ANALYSIS::"Review /tmp/blocked-* files created by architectural protection hooks", ARCHITECTURAL_ASSESSMENT::"Evaluate system architecture coherence, scalability, design pattern compliance", REGISTRY_INTEGRATION::"Use mcp__hestai__registry for official approval/rejection workflow", APPROVAL_FORMAT::"TECHNICAL-ARC
===SKILL:REVIEW_DISCIPLINE=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Methodology for evidence-based code review and confidence categorization" §1::CONFIDENCE_CATEGORIZATION CATEGORIES::[ CERTAIN::[ DEFINITION::"Can point to exact failure mode with concrete evidence", EVIDENCE::"Line number + reproduction steps + failure scenario", REPORT::ALWAYS ], HIGH::[ DEFINITION::"Strong evidence with minimal doubt", EVIDENCE::"Line number + reasoning + likely impact",
===SKILL:REVIEW_PREFLIGHT=== META: TYPE::SKILL VERSION::"1.2.0" STATUS::ACTIVE PURPOSE::"Mechanical prep delegation before review. Collects structured context brief via pal_chat so CRS spends tokens on judgement, not grunt work." §1::CORE AUTHORITY::ADVISORY[preflight_brief_structure] PHASE::PRE_REVIEW[runs_BEFORE_review-discipline⊕review-prioritization] COMPLEMENTS::[review-discipline<confidence>,review-prioritization<triage>] §2::PROTOCOL // CRS delegates preflight collection via mcp
Proper delegation patterns for Task() invocations with governance context injection
===SKILL:SYSTEM_ORCHESTRATION=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Core methodology for coordinating cross-boundary system coherence" §1::CORE_PHILOSOPHY ORCHESTRATION_PHILOSOPHY::[ STANDARDS_PROGRESSION::"PERCEIVE_SYSTEM_STATE→SYNTHESIZE_PATTERNS→VALIDATE_STANDARDS→ORCHESTRATE_PARALLEL→SYNTHESIZE_RESULTS→ENFORCE_DIRECTIVES", PARALLEL_QUEST_ARCHITECTURE::"Spawn multiple investigative streams via mcp tools, maintain coherence threads, coordinate convergence, synthesize finding
Core test infrastructure patterns for monorepo Vitest setup including global configuration, mocking patterns, and test standards
Testing patterns and conventions for HestAI MCP including pytest markers, TDD protocol, and coverage requirements
===SKILL:V9_AGENT_CREATION=== META: TYPE::SKILL VERSION::"1.0.0" STATUS::ACTIVE PURPOSE::"V9 blank-slate agent file creation per dream-team-architecture.md §2.2" SPEC_REFERENCE::docs/dream-team-architecture.md §1::CORE AUTHORITY::BLOCKING[v9_agent_file_commits⊕blank_slate_violations⊕phantom_task_profile_references<when_matrix_exists>] SCOPE::"Create and modify V9 agent .oct.md files per dream-team-architecture §2.2 blank-slate schema" // V9 agent files are ~50 line identity-only docum
Vercel preview deployment access patterns including automation bypass, protected preview authentication, and CI integration
===SKILL:OPERATIONAL_ANALYSIS=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Rigorous operational thinking for critical decisions and phase transitions" §1::CORE_METHODOLOGY METHODS::[ OWNER_MATRIX::"Who decides, who executes, who is accountable", EXPLICIT_THRESHOLDS::"Quantified criteria for GO/NO-GO decisions", RISK_QUANTIFICATION::"Probability × Impact with mitigation cost", SUCCESS_CRITERIA::"Measurable outcomes defining phase completion", GAP_ASSESSMENT::"Delta between curre
===SKILL:INFRASTRUCTURE_INTEGRITY=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Protocol for maintaining test infrastructure reliability and reproducibility" §1::CORE_CONSTRAINTS CONSTRAINTS::[ CI_REPRODUCIBILITY::"Local test execution must match CI environment exactly", STANDARDS_OBSERVABILITY::"Violations must be detectable through automated quality gates", ENVIRONMENT_ISOLATION::"Test credentials must never touch production systems", CROSS_APP_CONSISTENCY::"Shared test patterns
===SKILL:OBSERVATION_METHODOLOGY=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Protocol for comprehensive quality and security observation" §1::OBSERVATION_STEPS PROTOCOL::[ CONTEXT_GATHERING::"Requirements + standards + security policies + build artifacts", SYSTEMATIC_OBSERVATION::"Code review + architecture analysis + pattern detection + security scan", METRICS_COLLECTION::"Quantitative measurement + coverage analysis + complexity assessment", SECURITY_ASSESSMENT::"Vulnerability
===SKILL:PROPHETIC_INTELLIGENCE=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"System-wide failure pattern detection and early warning capability" §1::CORE_CAPABILITY PREDICTION_CAPABILITY::SYSTEM_WIDE_FAILURE_MODES ACCURACY_TRACKING::"80%+ historical accuracy for system-wide failure mode predictions (verified through retrospective analysis: predicted_failures / actual_failures ≥ 0.80)" VERIFICATION_METHOD::"Rolling 6-month accuracy measurement with pattern categorization and confidence ca
===SKILL:PATTERN_MASTERY=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Identify, name, and apply cross-domain and synthesis patterns with evidence." REQUIRES::[octave-literacy, octave-mastery] §1::PATTERN_LIBRARY BREAKTHROUGH_PATTERNS::[ CONSTRAINT_INVERSION::"The limitation IS the feature - flip the constraint", DOMAIN_COLLISION::"Borrow brilliance from unrelated fields", SUBTRACTION_INNOVATION::"Remove to improve", PERSPECTIVE_SHIFT::"Solve it like an expert from ano
===SKILL:DUAL_AXIS_VALIDATION=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Validation framework for both Requirements (WHAT) and Process (HOW)" §1::AXIS_1_REQUIREMENTS DIMENSION::"WHAT we build - North Star alignment" VALIDATION::"Every feature/component traces to North Star requirements" DEVIATION_TYPES::[feature_creep, scope_expansion, architecture_inflation, creative_replacement] ENFORCEMENT::"No implementation without North Star reference" §2::AXIS_2_PROCESS DIMENSION::"HOW we build
===TEST_VALIDATION_STANDARDS=== META: TYPE::SKILL VERSION::"1.0.0" STATUS::ACTIVE PURPOSE::"Test coverage assessment framework for PR code reviews" §1::CORE AUTHORITY::ADVISORY[test_quality_findings⊕coverage_gap_detection] SCOPE::PR_review_test_assessment[coverage⊕quality⊕TDD_compliance⊕missing_tests] MISSION::"Evaluate test adequacy for changed code — detect gaps, verify quality signals, enforce TDD discipline" §2::PROTOCOL COVERAGE_ASSESSMENT::[ 1::identify_changed_production_file
===SKILL:AGENT_CREATION=== META: TYPE::SKILL VERSION::"2.0.0" STATUS::ACTIVE PURPOSE::"v8.1 agent file creation and modification per octave-agents-spec" SPEC_REFERENCE::octave-agents-spec.oct.md §1::CORE AUTHORITY::BLOCKING[agent_file_commits⊕phantom_references⊕spec_violations] SCOPE::"Create and modify agent .oct.md files per octave-agents-spec v8.1" // Agent-expert owns WHAT goes in agent files; octave-specialist owns HOW OCTAVE is structured §2::PROTOCOL CREATION_SEQUENCE::[ 1:
Supabase test harness patterns including local Supabase setup, test user creation via Auth Admin API, RLS testing, migration testing (db_reset), seed sequences, rate limiting, and environment detection. Use when setting up Supabase testing infrastructure, creating test users, troubleshooting Supabase test failures, or implementing RLS validation. Triggers on: supabase test setup, test user creation, supabase local testing, RLS testing, migration testing, supabase test harness, auth test helpers.
===SKILL_CREATOR=== META: TYPE::SKILL VERSION::"3.2.0" STATUS::ACTIVE PURPOSE::"Spec-compliant skill and pattern creation per octave-skills-spec and octave-patterns-spec" SPEC_REFERENCE::[octave-skills-spec.oct.md,octave-patterns-spec.oct.md] §1::CORE AUTHORITY::BLOCKING[spec_violations⊕missing_required_fields⊕malformed_envelopes] SCOPE::[SKILLS::OCTAVE_envelope⊕§5::ANCHOR_KERNEL⊕YAML_optional, PATTERNS::OCTAVE_envelope_only⊕§5::ANCHOR_KERNEL_required] // Skills define WHAT agents do;
Reference for valid GitHub labels in HestAI-MCP repository to prevent label errors
Supabase operational knowledge for migrations, RLS optimization, MCP tool benchmarks, and ADR-003 compliance. Use when validating database migrations, optimizing Row-Level Security policies, checking MCP tool performance, or ensuring Supabase operational standards. Triggers on: migration validation, RLS patterns, Supabase benchmarks, ADR-003, database state tracking, schema governance.
===SKILL:DIAGNOSTIC_PROTOCOLS=== META: TYPE::SKILL VERSION::"1.0" STATUS::ACTIVE PURPOSE::"Empirical root cause identification: isolate, reproduce, evidence-gather, and confirm fix for implementation failures" // Complements error-triage (which classifies WHAT to fix first) — this covers HOW to find WHY it fails §1::SCOPE BOUNDARY::"error-triage→prioritizes_error_category; diagnostic-protocols→identifies_root_cause_within_category" AUTHORITY::BLOCKING[assumption_without_evidence⊕fix_w
===SKILL:AGENT_INTERVIEW=== META: TYPE::SKILL VERSION::"1.1.0" STATUS::ACTIVE PURPOSE::"Structured interview protocol for agent identity assessment. Extracts behavioral evidence for v8.1 agent file authoring with chassis-profile mapping." §1::CORE MISSION::"Extract the behavioral truth of an agent's identity, authority, and operational modes through structured questioning" AUTHORITY::"Any agent loading this skill can conduct agent interviews" OUTPUT::"Structured assessment document suit
===COGNITIVE_LOAD_ASSESSMENT=== META: TYPE::SKILL VERSION::"1.0.0" STATUS::ACTIVE PURPOSE::"Quantify cognitive burden of abstractions, interfaces, and developer-facing APIs" §1::CORE AUTHORITY::ADVISORY[cognitive_load_scoring⊕interface_complexity_assessment] SCOPE::API_surface_analysis⊕abstraction_depth_measurement⊕naming_clarity⊕state_management_burden PRINCIPLE::"Every abstraction has a cognitive tax — measure it before accepting it" §2::PROTOCOL METRICS::[ ABSTRACTION_DEPTH::count
Workflow for transforming prose into semantic OCTAVE structures. Covers tier selection, transformation phases, loss accounting, and decision rules. REQUIRES octave-literacy.
===COMPLEXITY_ASSESSMENT=== META: TYPE::SKILL VERSION::"1.0.0" STATUS::ACTIVE PURPOSE::"ESSENTIAL vs ACCUMULATIVE complexity taxonomy with SUBTRACT_UNTIL_BREAKS detection" §1::CORE AUTHORITY::BLOCKING[complexity_misclassification⊕false_positive_flagging] SCOPE::codebase_complexity_analysis⊕component_justification⊕simplification_triage TAXONOMY::[ ESSENTIAL::"Atlas_burden<justified_by_requirements⊕regulatory⊕domain_inherent>", ACCUMULATIVE::"Sisyphean_work<future_proofing⊕pattern_the
Ultra-high density compression using mythological atoms and semantic shorthand. Preserves soul and constraints at 60% compression for identity transmission, binding protocols, and extreme token scarcity.
===ROLLBACK_ORCHESTRATION=== META: TYPE::SKILL VERSION::"1.0.0" STATUS::ACTIVE PURPOSE::"Deployment rollback planning, testing procedures, and data migration rollback strategies" §1::CORE AUTHORITY::ADVISORY[rollback_plan_completeness⊕rollback_test_coverage] SCOPE::rollback_planning⊕rollback_testing⊕data_migration_reversal⊕deployment_strategy MISSION::"Ensure every deployment has a tested rollback plan before proceeding" §2::PROTOCOL ROLLBACK_PLAN_REQUIREMENTS::[ TRIGGER_CRITERIA::d
===SKILL:STRATEGIC_VALIDATION=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Validation methodology for long-term architectural viability" §1::VALIDATION_QUESTION CORE_QUESTION::"Will this architecture remain viable and maintainable 6 months from now, and what patterns suggest otherwise?" §2::EVIDENCE_REQUIREMENTS REQUIREMENTS::[ PATTERN_BASED_CLAIMS::"Must cite trend data or historical patterns", PREDICTIVE_VALIDATION::"Forecast methodology must be reproducible", STRATEGIC_COMPLIAN
Python pytest coverage analysis, gap identification, and TDD workflow for achieving 90%+ coverage
Comprehensive build philosophy including system awareness, MIP for code, decision frameworks, and wisdom paths. Prevents accumulative complexity through systematic thinking.
===SECURITY_THREAT_MODELING=== META: TYPE::SKILL VERSION::"1.0.0" STATUS::ACTIVE PURPOSE::"Security-focused code review lens with OWASP-aligned threat detection" §1::CORE AUTHORITY::BLOCKING[secrets_exposure⊕injection_vulnerabilities⊕auth_bypass] SCOPE::security_review[OWASP⊕auth_flows⊕dependency_risk⊕injection⊕secrets] MISSION::"Apply security threat modeling to code changes — detect vulnerabilities before they reach production" §2::PROTOCOL OWASP_REVIEW_CHECKLIST::[ A01_BROKEN_ACC
LLM-native structured communication format. Teaches OCTAVE syntax rules, canonical forms, and warning prevention for zero-error .oct.md authoring.
===INTEGRATION_ORCHESTRATION=== META: TYPE::SKILL VERSION::"1.0.0" STATUS::ACTIVE PURPOSE::"Interface audit, assembly sequencing, and integration verification methodology" §1::CORE AUTHORITY::BLOCKING[interface_contract_violations⊕schema_misalignment⊕error_code_inconsistency] SCOPE::integration_methodology⊕interface_audit⊕assembly_verification MISSION::"Ensure components integrate correctly through systematic interface validation and sequenced assembly" §2::PROTOCOL INTERFACE_AUDIT::[
===SKILL:MINIMAL_INTERVENTION=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Philosophy for preventing architectural over-engineering" §1::CORE_PRINCIPLES PRINCIPLES::[ ESSENTIAL_ARCHITECTURE::"Structure that directly enables system goals - user-facing capabilities", ACCUMULATIVE_ARCHITECTURE::"Layers that add complexity without measurable user benefit", SIMPLIFICATION_TEST::"Remove architectural components until functionality breaks, restore last essential layer", DAEDALIAN_PATH::
===SKILL:STANDARDS_REVIEW=== META: TYPE::SKILL VERSION::"2.0.0" STATUS::ACTIVE PURPOSE::"Methodology for evidence-based system standards documentation review with integrated finding prioritization. Provides structured analysis framework for reviewing architectural decisions, specs, rules, and standards artifacts against North Star alignment, cross-document consistency, structural completeness, and downstream impact." §1::STANDARDS_REVIEW_DIMENSIONS DIMENSIONS::[ ALIGNMENT::[ DEFIN
===E2E_TEST_STRATEGY=== META: TYPE::SKILL VERSION::"1.0.0" STATUS::ACTIVE PURPOSE::"End-to-end validation design, user journey mapping, and integration sign-off methodology" §1::CORE AUTHORITY::ADVISORY[test_strategy_design⊕coverage_gaps⊕sign_off_evidence] SCOPE::e2e_test_design⊕execution_planning⊕integration_sign_off MISSION::"Design E2E validation that proves system behavior across component boundaries" §2::PROTOCOL TEST_DESIGN::[ 1::map_user_journeys<critical_paths⊕happy_paths⊕er
===SKILL:SYNTHESIS_FOUNDATION=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Methodology for third-way synthesis and tension transcendence" §1::SYNTHESIS_METHODOLOGY STEPS::[ STEP_1_TENSION_MAP::"Identify explicit oppositions between Wind expansion and Wall constraint", STEP_2_KERNEL_FIND::"Locate where BOTH positions are correct - the shared truth", STEP_3_PATTERN_DISCOVER::"Find the organizing principle that unifies apparent contradiction", STEP_4_THIRD_WAY_FORGE::"Create emergen
===SKILL:REVIEW_CONTEXT=== META: TYPE::SKILL VERSION::"1.0.0" STATUS::ACTIVE PURPOSE::"Path-specific review instructions for CRS. Encodes domain knowledge about file categories, review focus areas, and format exceptions to prevent false positives and guide reviewers to high-value findings." §1::CORE AUTHORITY::ADVISORY[review_focus_guidance] PHASE::PRE_REVIEW[loaded_before_CRS_begins_review_judgement] COMPLEMENTS::[review-preflight<context_collection>,review-discipline<confidence>,revie
===SKILL:DESIGN_DECISION_GATE=== META: TYPE::SKILL VERSION::"2.0" STATUS::ACTIVE PURPOSE::"Validation gate for design decisions requiring explicit stakeholder choice and documented rationale" §1::CORE MISSION::"Prevent design decisions from proceeding without explicit stakeholder choice and evidence" AUTHORITY::"BLOCKING — no design decision passes without documented rationale and stakeholder selection" §2::PROTOCOL GATE_SEQUENCE::[ 1::ANALYZE::"Review design alternatives against con
===SKILL:INTEGRITY_DEFENSE=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Methodology for defending test integrity against manipulation" §1::DETECTION_PROTOCOL TRIGGER_PHRASES::[ "workaround", "let me fix the test", "run a simpler test", "try a simpler fix", "adjust the expectation", "make the test pass", "skip this test", "comment out", "lower the bar" ] §2::INTERVENTION_PROTOCOL STEPS::[ DETECT::"Pattern matching on trigger phrases and anti-pattern recognition", HALT::"Immedia
Python code style guidelines for HestAI MCP including type hints, imports, error handling, and docstrings
Document placement using timeline test and HestAI visibility rules. Maps artifacts to .hestai-sys/, .hestai/, docs/, .hestai/state/ with phase artifact rules, format selection, anti-patterns, and documentation-first protocols.
CI/CD pipeline configuration for monorepo testing including GitHub Actions workflows, Turborepo integration, quality gates, and preview deployments
===SKILL:VALIDATION_METHODOLOGY=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Rigorous 6-step reality enforcement protocol" §1::CORE_PROTOCOL VALIDATION_METHODOLOGY::[ STEP_1_NATURAL_LAW::"Identify physics constraints, thermodynamic limits, information theory bounds", STEP_2_RESOURCE_REALITY::"Inventory actual available resources (time, people, tools, budget) with evidence", STEP_3_CAPABILITY_ASSESSMENT::"Validate team skills, tool availability, knowledge gaps against requirements",
===SKILL:CLARIFICATION_GATE=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Ambiguity detection and resolution protocol before implementation" §1::GATE_TRIGGER CONDITION::"Apply when ANY of the following are unclear in the build plan" §2::AMBIGUITY_DETECTION SIGNALS::[ PRIORITY_CONFLICTS::"Multiple tasks could be started - which first?", DEPENDENCY_CHOICES::"Task specifies options without clear selection", INTEGRATION_UNCLEAR::"How should component X connect to existing system Y?",
===SKILL:SYSTEM_STEWARDSHIP=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Protocol for meta-observation, documentation preservation, and pattern recognition" §1::CORE_METHODOLOGY PROTOCOL::[ META_OBSERVATION::"System patterns + knowledge evolution + insight formation", PRESERVATION_EXCELLENCE::"Documentation fidelity + version integrity + citation discipline", PATTERN_SYNTHESIS::"Cross-domain recognition + emergent understanding + wisdom extraction", GIT_STEWARDSHIP::"Version mast
Advanced semantic vocabulary, holographic contracts, and structural patterns for OCTAVE. REQUIRES octave-literacy. Extends literacy with mythology, archetype annotation, v6 contracts, and anti-pattern rules.
Systematic detection of placeholder implementations, stubs, and hidden incomplete code. Three-pattern taxonomy with search strategies
===SKILL:REVIEW_PRIORITIZATION=== META: TYPE::SKILL VERSION::"2.0.0" STATUS::ACTIVE PURPOSE::"Severity-ordered finding triage for CRS reviews. Context-adaptive: PR reviews get display budget, standalone/audit reviews report all findings." §1::CORE AUTHORITY::ADVISORY[finding_ordering⊕batch_triage] COMPLEMENTS::[review-discipline<confidence_levels>,constructive-feedback<presentation>] §2::PRIORITY_TIERS // Order: P0→P5. Within each tier: CERTAIN→HIGH→MODERATE. P0_SECURITY::injection⊕aut
===SKILL:OPERATING_DISCIPLINE=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Enforcement of system-wide operating discipline gates and boundaries" §1::OPERATING_ESSENTIALS PHASE_GATES::"D1(NORTH-STAR)→D2(DESIGN)→D3(BLUEPRINT)→B0(VALIDATION)→B1(BUILD-PLAN+STOP)→B2(TDD)→B3(INTEGRATION)→B4(HANDOFF)" QUALITY_GATES::"TDD(failing_test_first)→TMG_CHECKPOINT(T2+:TMG_must_APPROVE)→CodeReview(every_change)→Tests(must_pass)→Security(scan_required)" RACI_CONSULTATIONS::"critical-engineer(tactical)→pri
Core operating manual for the Holistic Orchestrator. Enforces lane discipline (zero implementation), oa-router delegation, quality gating, debate escalation, and emergency protocols.