pot

Evaluate technology stacks and generate evidence-based POT.md documents.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Wizarck/iguanatrader --skill pot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pot
Source: https://github.com/Wizarck/iguanatrader/tree/main/skills/pot
Command: npx skills add https://github.com/Wizarck/iguanatrader --skill pot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Develops POT (Proof of Technology) documents that validate which solution stacks best deliver the use cases identified in Business Strategy, producing platform capability comparisons, use case assessments, economic analysis, and technology recommendations. Use when creating or updating a POT.md, when evaluating technology stacks for an offering, when comparing platform options, or when the user says "proof of technology", "POT", "technology evaluation", or "stack comparison". Calls /qa-pot for validation.

Core Features & Use Cases

  • Produce POT.md documents with stack evaluations, use-case ratings, economic analysis, and technology recommendations.
  • Reference the standard POT workflow (template, BS summaries, Use Cases, research) to ensure traceability and consistency.
  • Trigger POT generation in response to user requests like "proof of technology", "POT", "technology evaluation", or "stack comparison" and route for validation via /qa-pot.

Quick Start

Provide an OFFER ID and trigger POT validation to generate a validated POT.md.

Frequently Asked Questions about pot

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

FAQPage Schema
What is a proof of technology document for evaluating software architecture?

Yes, you can generate a POT document by providing an OFFER ID. The system evaluates candidate technology stacks against validated business-use cases and triggers validation to produce a self-contained POT.md file with stack recommendations and scoring.

How do I compare technology stacks for a specific business use case?

To compare technology stacks, evaluate candidate platforms against validated business-use cases to generate evidence-based ratings. This process produces stack recommendations with actionable use-case scoring and economic analysis for downstream scoping decisions.

What inputs do I need to start a technology evaluation for my offering?

You need an OFFER ID and validated business strategy inputs including use cases and research files. These inputs ensure source traceability and consistency when generating the POT.md document with stack evaluations and technology recommendations.

Does the technology evaluation process enforce source traceability for research files?

Yes, the technology evaluation enforces strict source traceability to 00_Research files. It follows template rules, assigns sequential D-POT IDs, and outputs a self-contained POT.md including overview, scoring, economics, and decisions based on validated evidence.

When should I use a POT instead of a general architecture decision record?

Use a POT when you need to validate specific solution stacks against business use cases with economic analysis and platform capability comparisons. It is designed for the BS to POT to OS pipeline, producing stack recommendations with actionable use-case ratings for downstream scoping.