Poc

Build a throwaway proof-of-concept. Speed over quality. Hardcoded values OK, ugly code OK, no error handling beyond crash prevention. This code is NEVER going to production — /integrate will rebuild fresh. The skill's most important step is the learnings write-back at the end, which routes discoveries to stack.md / decisions.md / learnings.jsonl so /integrate can use them without ever reading POC code. Proactively invoke this skill after /scope when the FDE says "let me build a quick thing", "let me try this", "time to prototype", "let's hack something together", or otherwise indicates they're

49 stars 5 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Dan-Cleary/fdestack --skill poc
Manual install
git clone --depth 1 https://github.com/Dan-Cleary/fdestack.git /tmp/fdestack
mkdir -p ~/.claude/skills
cp -r /tmp/fdestack/skills/poc ~/.claude/skills/poc

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# /poc

Build a throwaway POC. Optimized for shipping signal fast, not code longevity.

## Step 0: Parse inputs

The customer name is the first argument.

Optional flag: `--purpose value | showcase | feasibility`
- **value** (default) — prove a financial case. POC must produce numbers defensible to a stakeholder. Hardcoded inputs OK, but the *output* must match what was framed in `/value-frame`.
- **showcase** — prove the demo path. POC must demo well in 60 seconds. Visual/UX matters more than correctness. Hardcoded happy path acceptable; failure modes ignored.
- **feasibility** — prove something is possible at all. POC must answer one yes/no question (can we do X?). Output is technical evidence, not a demo.

The three modes change what "done" means; pick deliberately. If unclear, ask the FDE: "What needs to be true Friday for this POC to have been worth the time?" Answer maps cleanly to one purpose.

Set `CUSTOMER_NAME` and `PURPOSE` (default `value`).

## Step 1: Check session marker

Same as `/scope` / `/discovery` / `/value-frame`:

```bash
MARKER="/tmp/fdestack-session-$CUSTOMER_NAME"
if [ -f "$MARKER" ]; then
  MARKER_TS=$(grep '^ts=' "$MARKER" | cut -d= -f2)
  AGE=$(( $(date +%s) - MARKER_TS ))
  [ "$AGE" -lt 43200 ] && echo "MARKER_OK=true" || echo "MARKER_STALE=true"
else
  echo "MARKER_MISSING=true"
fi
```

If missing or stale: print "Run /customer-context $CUSTOMER_NAME first." Stop.

## Step 2: Verify scope exists
Read the full skill on GitHub

Details

Skill name
poc
Path
skills/poc/SKILL.md
License
MIT
Repo updated
19 May 2026

FAQ

What does the Poc skill do?

Build a throwaway proof-of-concept. Speed over quality. Hardcoded values OK, ugly code OK, no error handling beyond crash prevention. This code is NEVER going to production — /integrate will rebuild fresh. The skill's most important step is the learnings write-back at the end, which routes discoveries to stack.md / decisions.md / learnings.jsonl so /integrate can use them without ever reading POC code. Proactively invoke this skill after /scope when the FDE says "let me build a quick thing", "let me try this", "time to prototype", "let's hack something together", or otherwise indicates they're

How do I install the Poc skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Dan-Cleary/fdestack --skill poc. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Poc popular?

It lives in Dan-Cleary/fdestack, which has 49 GitHub stars and 5 forks.

Related skills

Customer Context

49

Dan-Cleary/fdestack

Load a customer's context at the start of every session. Run this before any other FDEstack skill. Reads all 7 context files, surfaces drift since last session, asks what's new, and commits updates. Proactively invoke this skill (do NOT answer customer-specific questions directly) when the user references a customer name in an FDE ops repo without context being loaded this session. Always the first skill in a customer session — every other FDEstack skill requires its session marker. Usage: /customer-context <customer-name> Voice triggers: "load <customer>", "start session with <customer>", "wh

Marketing, Sales & Business

Discovery

49

Dan-Cleary/fdestack

Process any inbound source of customer context — meeting transcript, prior FDE's handoff notes, AE/sales briefing, customer-side RFP response, prior Discovery Workshop output, or your own raw notes. Extracts new stack info, stakeholders, stated problem, real problem, open questions, and context conflicts. Updates customer context files and commits. Proactively invoke this skill (do NOT just summarize) when the user pastes call notes, meeting transcripts, AE briefings, RFP responses, handoff docs, or any inbound document about a customer. Triggers on phrases like "I just had a meeting", "here a

Marketing, Sales & Business

Engagement Retro

49

Dan-Cleary/fdestack

Weekly retrospective for a single customer engagement. Reads commit history, recent discovery/scope/value-frame/poc/integrate files, and current blockers/unknowns. Produces a structured retro: what shipped, what's stuck, what we learned, what's next. Optional cross-customer learnings write-back for patterns worth remembering. Distinct from gstack's /retro (which is engineering-retro per-codebase). Proactively invoke this skill on Fridays or end-of-week, or when the FDE asks "where did the week go", "weekly retro", "what shipped this week", or seems to be wrapping up an engagement phase. Always

Marketing, Sales & Business

Python Best Practices

43

jefflester/claude-skills-supercharged

Python development best practices including PEP 8 style guidelines, type hints, docstring conventions, and common patterns. Use when writing or modifying Python code.

Software Development

Validate Business Logic Against Code

47

meirm/reverse-engineering-skill

Verifies whether documented business logic is actually implemented by mapping BL rules to code evidence. Flags rules as implemented, partially implemented, contradicted, or not found. Use when validating business logic documents, checking code coverage against requirements, or verifying BL-to-code alignment.

Software Development

Golang Backend

47

mujez/claude-skills

Expert Go backend engineer skill. Use when writing Go services, APIs, microservices, CLI tools, or libraries. Covers architecture, concurrency, testing, database patterns, gRPC, REST APIs, error handling, and Go best practices.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.