Towa: Technical Decisions

Plugin technical-decisions from marketplace tomwangowa in tomwangowa/agent-skills. Commands read from the repo's manifest — today.

Skills (16)

• assumption-extractor

  Systematically extract explicit and implicit assumptions from technical documents, design plans, or feasibility assessments. Classifies each assumption by visibility (explicit/implicit), verification status (verified/unverified/falsified), recommended verification method, and risk impact. Use when r

• brainstorming

  Use when the agent needs to turn a vague idea into an approved design before implementation, or when a user wants to grill / stress-test a plan or idea (triggers: grill, 烤, stress-test). Apply to new features, architecture changes, refactoring, and workflow design. Interview one decision at a time w

• critical-research

  Falsification-first research skill that actively seeks counter-evidence before supporting evidence to eliminate cognitive biases and ensure rigorous, objective conclusions.

• deep-reading

  Use when deeply reading existing documents, learning an unfamiliar article or paper, extracting mental models, comparing source disagreements, identifying knowledge gaps, or turning source material into reusable understanding; supports progressive first-pass, Deep, and focused Deep Dive reading, but

• micro-poc-validator

  Empirically validate technical assumptions through minimal code experiments (5-30 min spikes). Use when a tech-feasibility assessment or design document contains claims that can be proven or disproven by running actual code. Triggered by "validate this assumption", "can X actually do Y?", "prove it

• narrative-auditor

  Audit external narratives (articles, posts, marketing copy) against primary sources, or speak on behalf of the user as their AI proxy. Use when asked to "fact-check", "verify this article", "audit this claim", "help me respond", "speak for me", or "supplement context".

• research-cross-validator

  Cross-validate technical claims using multiple independent verification strategies (official docs, counter-examples, source code inspection). Use when a tech-feasibility report, design document, or any technical analysis contains claims that were verified by only one method or one AI session. Trigge

• research-synthesis

  Use after running 2+ research skills (critical-research, tech-feasibility, narrative-auditor, codebase-audit) to synthesize findings into a unified decision document. Resolves conflicts between sources, weighs evidence, and produces an actionable recommendation.

• role-orchestrator

  Orchestrates a multi-role development pipeline (PM → RD) using subagent dispatch. Reads project-profile.yaml to calibrate role behavior by project size. Each role runs in an isolated subagent to prevent context pollution. Includes gate checks for user approval between phases. Triggered by "role orch

• role-pm

  PM (Product Manager) role for the multi-agent role system. Produces structured requirements artifacts calibrated by project size (small/medium/large). Invoked by role-orchestrator via subagent dispatch, or directly for standalone requirements work. Triggered by "PM analysis", "requirements gathering

• role-rd

  RD (Developer) role for the multi-agent role system. Produces structured design artifacts calibrated by project size (small/medium/large), taking PM requirements as input. Invoked by role-orchestrator via subagent dispatch, or directly for standalone design work. Triggered by "RD analysis", "technic

• spec-gap-finder

  Analyze PM spec and UI wireframe from an RD perspective to find gaps, ambiguities, and undefined edge cases before implementation starts. Produces a structured pre-dev question list ready for a single alignment meeting with PM/Designer. Use when: (1) RD receives a new feature spec or wireframe and w

• tech-feasibility

  Use when evaluating whether a specific technology, tool, or approach can solve a given problem before committing to implementation. Triggered by questions like "can X do Y?", "will X work for Y?", "is X feasible for Y?", or "should I use X to achieve Y?

• tech-research-pipeline

  Orchestrates a full technical research workflow by chaining specialized skills in sequence: brainstorming → tech-feasibility → assumption-extractor → micro-poc-validator → critical-research → narrative-auditor → research-cross-validator → research-synthesis. Use when evaluating a technology choice,

• technical-proposal-review

  Use when the user asks to review a technical wiki, design proposal, RFC, or enhancement proposal while lacking project context ("review this enhancement proposal", "I don't know this project", "help me understand this technical wiki", "review this RFC", "technical proposal review"), or wants informe

• ui-design-analyzer

  Analyze UI/UX design from screenshots. Use this Skill when the user asks to analyze UI design, review interface screenshots, check design quality, evaluate user experience, or get design improvement suggestions.

Hooks (1)

• SessionStart

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/policy.py"

Similar plugins