Stream Coding
Documentation-first development methodology. The goal is AI-ready documentation - when docs are clear enough, code generation becomes automatic. Triggers on "Build", "Create", "Implement", "Document", or "Spec out". Version 3.5 adds Phase 2.5 Adversarial Review and renames internal verification to Spec Gate (structural completeness). Clarity Gate is now a separate standalone tool for epistemic quality.
Install
npx skills add frmoretto/stream-coding --skill stream-codinggit clone --depth 1 https://github.com/frmoretto/stream-coding.git /tmp/stream-coding
mkdir -p ~/.claude/skills
cp -r /tmp/stream-coding/. ~/.claude/skills/stream-codingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Stream Coding v3.5: Documentation-First Development ## ⚠️ CRITICAL REFRAME: THIS IS A DOCUMENTATION METHODOLOGY, NOT A CODING METHODOLOGY **The Goal:** AI-ready documentation. When documentation is clear enough, code generation becomes automatic. **The Insight:** > "If your docs are good enough, AI writes the code. The hard work IS the documentation. Code is just the printout." **v3.5 Core Additions:** 1. Phase 2.5 Adversarial Review — stress-test specs with a hostile critic before execution. New time allocation: 40/40/5/10/5. 2. Renamed internal 13-item checklist to **Spec Gate** (structural completeness for code generation) > **Two-gate pipeline — know the difference:** > - **Spec Gate** (13 items, this skill) → *"Can AI execute this without asking questions?"* > - **Clarity Gate** (9 points, separate tool) → *"Will AI mistake assumptions for facts?"* > > Spec Gate → Clarity Gate → Adversarial Review → Verified Specification → Execution --- ## CHANGELOG | Version | Changes | |---------|---------| | 3.0 | Initial Stream Coding methodology | | 3.1 | Clearer terminology, mandatory Spec Gate | | 3.3 | Document-type-aware placement (Anti-patterns, Test Cases, Error Handling in implementation docs) | | 3.3.1 | Corrected time allocation (40/40/20), added Phase 4, added Rule of Divergence | | 3.4 | Complete 13-item Spec Gate, scoring rubric with weights, self-assessment questions, 4 mandatory section templates, Documentation Audit integrated into Phase 1 |
Details
- Skill name
stream-coding- Repository
- frmoretto/stream-coding
- Repo updated
- 26 February 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Stream Coding skill do?
Documentation-first development methodology. The goal is AI-ready documentation - when docs are clear enough, code generation becomes automatic. Triggers on "Build", "Create", "Implement", "Document", or "Spec out". Version 3.5 adds Phase 2.5 Adversarial Review and renames internal verification to Spec Gate (structural completeness). Clarity Gate is now a separate standalone tool for epistemic quality.
How do I install the Stream Coding skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add frmoretto/stream-coding --skill stream-coding. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Stream Coding popular?
It lives in frmoretto/stream-coding, which has 98 GitHub stars and 7 forks, and is included in 1 curated skill list.
Related skills
Faq Shortcuts
133kishormorol/cli-faq-shortcuts
Turn the questions and instructions a user keeps typing into a project into short slash-command skills, mined from their real Claude Code, Codex and Cursor session history and git log. The shortcuts load in Claude Code, Codex and Cursor. Use when the user says they ask the same things every day, wants an FAQ or shortcuts or abbreviations for a project, wants to "stop writing the whole command", or asks what they repeat most.
Vibe
121pcx-wave/vibe-skill
Delegate a coding task to Mistral Vibe and supervise the result via git diff. Trigger: /vibe <instruction>. Claude orchestrates, Vibe codes. Also handles /vibe-report [--since N] [--project NAME] [--fails] — token/cost/failure report.
Requirement Ledger
125adand-91/gpt-6-astra-skill
Run the advanced, evidence-bound Requirement Ledger CLI workflow from an explicit target, window, scope, and files; create private evidence, candidates, exact report bindings, and a read-only handoff check. Use for reproducible review/continuity, not the Codex host-selected quick audit, history discovery, autonomous edits, or publication.
Codex Multi Profile
93Hung2124/codex-multi-profile
Multi-workspace profile router, MCP server (.mcp.json) security auditor, and CLAUDE.md <-> AGENTS.md instruction bridge for Claude Code and OpenAI Codex. Isolates Enterprise, Open-Source Maintainer, and Personal profiles across ~/.claude and ~/.codex, and provides a native workspace switcher for the Microsoft Store Codex app on Windows.
Venice API Keys
160veniceai/skills
Manage Venice API keys. Covers GET/POST/PATCH/DELETE /api_keys, GET /api_keys/{id}, GET /api_keys/rate_limits, GET /api_keys/rate_limits/log, the two-step /api_keys/generate_web3_key wallet flow, INFERENCE vs ADMIN key types, per-key consumption limits (USD / DIEM) with EPOCH / MONTH / LIFETIME reset windows, and per-key modelPrivacy (ALL / PRIVATE_TEXT / PRIVATE_ONLY).
Codex Collab
99Kevin7Qi/codex-collab
Use when the user asks to invoke, delegate to, or collaborate with Codex on any task. Also use PROACTIVELY when an independent, non-Claude perspective from Codex would add value — second opinions on code, plans, architecture, or design decisions.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.