snowfluke

My Tech Lead Flow — AI skill for Claude Code

AI community

AI Agent Skills library to facilitate technical lead in a software project.

How to install My Tech Lead Flow

This entry records only its repository, not the path inside it, so there is no exact command to give. Open snowfluke/my-tech-lead-flow and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What My Tech Lead Flow does

AI Agent Skills library to facilitate technical lead in a software project.

Alternatives in AI

Claude Flow — An enterprise-grade AI orchestration platform that revolutionizes how developers build with AI 22.2k ★
Flow Define — Multi-AI requirements scoping using Codex and Gemini CLIs (Double Diamond Define phase) 2.8k ★
SEO Geo Claude Skills — 20 SEO & GEO skills for Claude Code, Cursor, Codex, and 35+ AI agents 888 ★

README

Claude Code Skills

Personal skill library for Claude Code. The core of this repository is a **technical lead pipeline**: a sequence of skills that takes a product idea from raw user stories all the way to a reviewed, documented, deployable codebase. Each stage is a skill that reads the artifacts produced by the previous stage and writes the next one, so the project documentation stays consistent and every decision is traceable back to an acceptance criterion.

The technical lead pipeline

The pipeline runs in order. Steps 1 and 3 are manual (the human supplies or edits the source material); every other step is a skill invoked with `/`. Step 0 is optional, for projects that start from an idea rather than a written spec.

Step	Stage	Skill	Produces
0	Discover (optional)	`product-discovery`	The step-1 requirements table, elicited by interview, when no user stories or AC exist yet
1	Capture requirements	(manual or step 0)	A Markdown table of user stories, acceptance criteria, and a sprint breakdown
2	Groom	`grooming`	Engineering's gaps before commitment. Two modes: blast every question into a file with recommendations (to take to a BA/PO), or interview the user one question at a time and refine the US/AC from their answers
3	Refine	(manual)	Edits to the US and AC based on grooming output
4	Format	`us-ac-formatter`	`docs/business/`: `user-story.md`, `sprint-breakdown.md`, and per-sprint Gherkin acceptance criteria
5	Specify	`technical-spec`	`docs/technical-specs/`: numbered `NN-topic.md` files plus `_index.md`, including ad-hoc trailing specs. Grills on tech stack and tooling first
6	Spec the API	`api-spec`	`docs/api-specs/`: numbered `NN-topic.md` files plus `_index.md`, deriving every operation, its inputs/outputs, errors, and access rules from the module definitions and data model, in the project's chosen protocol (REST/GraphQL/gRPC/SOAP)
7