Menü
Validate design hypotheses via code experiments, codebase analysis, and external research.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Agent-only canonical output templates for rp1 artifacts. Load when producing structured markdown to ensure format consistency and routing metadata.
Ask about rp1 capabilities, discover skills, and get workflow guidance.
Evidence-gated tech debt and bloat detection. Scouts signals, ranks by materiality, validates by refutation, reports up to 5 findings with actions.
Synchronizes user-facing documentation with the current knowledge base through validate -> stale gate -> scan -> approval -> process orchestration.
Orchestrates parallel KB generation using spatial analysis and a map-reduce architecture with incremental and feature-learning modes.
Analyzes systems holistically to provide strategic recommendations balancing cost, quality, performance, complexity, and business objectives with quantified trade-offs.
| name | validate-hypothesis |
| description | Validate design hypotheses via code experiments, codebase analysis, and external research. |
| allowed-tools | Bash(echo *), Bash(rp1 *) |
| metadata | {"category":"investigation","is_workflow":false,"version":"1.0.0","tags":["feature","validation","design"],"created":"2025-11-29T00:00:00.000Z","updated":"2026-02-26T00:00:00.000Z","author":"cloud-on-prem/rp1","arguments":[{"name":"FEATURE_ID","type":"string","required":true,"description":"Feature identifier whose hypotheses to validate (kebab-case)"}],"sub_agents":["rp1-dev:hypothesis-tester"]} |
Invokes hypothesis-tester agent to validate design assumptions.
{workRoot}/features/{FEATURE_ID}/hypotheses.md MUST exist{% dispatch_agent "rp1-dev:hypothesis-tester" %} FEATURE_ID: {FEATURE_ID} Validate all PENDING hypotheses for this feature. {% enddispatch_agent %}
Agent actions: load hypotheses.md -> parse PENDING -> validate via experiment/analysis/research -> document findings w/ evidence -> update status CONFIRMED|REJECTED -> cleanup temp artifacts -> report summary
Parse agent output. If JSON block w/ type: "rejected_hypotheses":
{
"type": "rejected_hypotheses",
"hypotheses": [...],
"hypotheses_path": "..."
}
For each rejected:
{% ask_user "{id} REJECTED: {statement}. Evidence: {evidence_summary}. Domain knowledge confirms valid?", options: "Accept rejection", "Override - I confirm valid" %}
If "Override":
REJECTED -> CONFIRMED_BY_USER**User Override**: User confirmed validity based on domain knowledge.If "Accept rejection": No change (status remains REJECTED)
Display validation summary. Note any user overrides.