dhpk-feasibility-studylisted

# Feasibility Study Skill ## Supplementary Agent For each solution option, dispatch background exploration: Agent({ description: "Explore feasibility of solution option", subagent_type: "general-purpose", prompt: `Research the feasibility of: <solution description> Evaluate technical feasibility, effort, risk, extensibility, and maintenance cost.` }) ## When NOT to Use - Already have a tech spec (use `/deep-analyze`) - Need implementation, not analysis (use `/dhpk:dhpk-codex-implement`) - Quick question (use `/dhpk:dhpk-codebase-exploration --explain` or `/dhpk:dhpk-codex-architect`) ## Workflow ``` Decompose → Constraints → Code research → Solutions → Codex discussion → Decision → Report ``` ### Phase 1: Requirement Decomposition **Input source priority**: 1. If `canonical_docs.requirements` is non-null → consume as authoritative requirement source, validate via 5-Why 2. Otherwise → extract requirements from user input via 5-Why analysis Use "5 Why" to uncover essence: 1. Surface requirement (what user asks for) 2. Underlying problem (why they need it) 3. Success criteria (quantifiable acceptance) ### Phase 2: Constraint Analysis Inventory constraints by type (Technical, Business, Resource, Compatibility) with flexibility rating. ### Phase 3: Code Research Research existing codebase: - Related modules and reusable logic - Existing design patterns - Tech debt to work around ### Phase 4: Solution Exploration Brainstorm 2-3+ solutions, each with: 1. Core i