lean-dev-flow

Guides lean implementation loops with tiered test selection and worktree management for Linear tasks.

1|Updated Sep 15, 2026
One-click install
npx skills add https://github.com/amoai-tech/mdeai --skill lean-dev-flow-amoai-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lean-dev-flow
Source: https://github.com/amoai-tech/mdeai/tree/main/.claude/skills/lean-dev-flow
Command: npx skills add https://github.com/amoai-tech/mdeai --skill lean-dev-flow-amoai-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Developers waste minutes per task running full test suites, lint, and builds on every small change when targeted verification would suffice. This Skill replaces the floor-on-every-change pattern with a 7-step loop that runs the right verification at the right time. ## Core Features & Use Cases - 7-Step Lean Loop: Read, implement, run targeted T1 test, typecheck, commit specific files, push, and open a PR without redundant local CI reproduction. - Test Tier Selection: Choose between T1 targeted vitest (~2s), T2 domain tests (~5s), or T3 floor (~3min) based on the shape of the change. - Worktree Management: Bootstrap, audit, and clean isolated git worktrees per Linear issue using wt-new, wt-audit, and wt-clean scripts. - Use Case: When starting Linear issue SAN-500 for an event filter UI change, create a worktree, edit the component, run only its test file plus tsc --noEmit, commit, and let CI handle lint, build, and the full suite. ## Quick Start Ask the AI to start implementing Linear issue SAN-500 using the lean loop with the appropriate test tier for the files being changed.

Frequently Asked Questions about lean-dev-flow

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

FAQPage Schema
How do I choose which tests to run for a small code change?

Run the lowest test tier that proves the change: T1 targeted vitest on the single changed file for isolated edits, T2 domain tests for shared hooks or libs, and T3 floor only once at PR time. CI handles lint, build, and the full suite.

How to set up a git worktree for a Linear issue branch?

Run bash mdeapp/scripts/wt-new.sh with the issue number and slug to create a branch and worktree from origin/main under mdeapp/workspace/. If the script does not exist, use git worktree add directly with a new branch based on origin/main.

Should I run npm run build locally before committing?

No, for library or hook changes use npx tsc --noEmit which answers type questions in about 5 seconds instead of a 90-second build. CI runs the full next build, lint, and test suite on every push.

When should I run the full test suite instead of targeted tests?

Run the full floor suite once when opening a PR, not per commit. Targeted T1 tests before each commit plus typecheck before push provide sufficient confidence while CI owns the complete verification.

Why avoid git add -A when committing task changes?

git add -A risks staging .env files, work-in-progress files, or unrelated changes. Always stage specific files with git add followed by explicit paths to keep commits clean and reviewable.