prototype

Prove technical feasibility with a minimal prototype and a YES/NO/PARTIAL verdict.

351|31|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/ryanthedev/code-foundations --skill prototype
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/ryanthedev/code-foundations/tree/main/skills/prototype
Command: npx skills add https://github.com/ryanthedev/code-foundations --skill prototype

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams determine technical feasibility by delivering a minimal prototype that provides an answer to one atomic question, reducing risk before full implementation.

Core Features & Use Cases

  • Atomic question proof: Validate a single capability with a minimal code artifact.
  • 6-phase workflow: SCOPE, CONTEXT, MINIMUM, EXECUTE, VERIFY, CAPTURE to guide decision making.
  • Prototype logging: Produce a documented YES/NO/PARTIAL verdict and store learnings in docs/prototypes/.

Quick Start

Define ONE atomic question to prove and initiate the six-phase prototype workflow.

Frequently Asked Questions about prototype

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

FAQPage Schema
How do I prove technical feasibility with a minimal prototype before full implementation?

A minimal prototype proves technical feasibility by answering one atomic question through a 6-phase workflow: SCOPE, CONTEXT, MINIMUM, EXECUTE, VERIFY, and CAPTURE, producing a YES/NO/PARTIAL verdict.

What is the best workflow for validating a single technical capability with pseudocode?

The best workflow for validating a single technical capability with pseudocode follows six phases: SCOPE, CONTEXT, MINIMUM, EXECUTE, VERIFY, and CAPTURE, guiding teams from question definition to a documented feasibility verdict.

Do I need to enforce branching discipline when creating a prototype?

Yes, you need to enforce branching discipline when creating a prototype. This ensures code changes remain isolated and structured while validating the atomic question during the execution phase.

How does a prototype log help reduce risk in software engineering?

A prototype log reduces risk by capturing the verified YES/NO/PARTIAL feasibility verdict and contextual learnings in the docs/prototypes directory, ensuring teams avoid full implementation of unproven capabilities.

Can I use module design reviewing alongside pseudocode programming for prototyping?

Yes, you can and must use module design reviewing alongside pseudocode programming for prototyping. Invoking both ensures the minimal code artifact aligns with structural standards while proving the atomic question.

When should I not use a minimal prototype approach for feasibility testing?

You should not use a minimal prototype approach when the technical capability is already proven or fully understood, as the workflow targets reducing uncertainty about specific capabilities before committing to full implementation.