skills.rest
luyzkk
luyzkkCOMMUNITY
Explore all skills by this author →
GitHub

quick-plan

Convert medium-complexity development tasks into 3–7 step executable plans with verify criteria.

Updated Mar 8, 2026
Search Tags:#tdd#code scaffolding#verification#lint#test workflow#step-by-step execution#mini-planning
One-click install
npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill quick-plan-luyzkk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quick-plan
Source: https://github.com/luyzkk/Anti-Vibe-Coding/tree/main/skills/quick-plan
Command: npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill quick-plan-luyzkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill removes hesitation and wasted cycles by converting a vague or medium-sized coding task into a tight, verifiable execution plan before any work starts.

Core Features & Use Cases

  • Mini-planning without extra files: Produces a 3–7 step step/verify plan inline in the same session, avoiding heavyweight planning artifacts on disk.
  • Step-by-step execution guardrails: Guides execution one atomic step at a time with clear verification criteria and a final validation gate (tests + lint).
  • TDD-aligned when applicable: Keeps tests-first behavior when the task allows it, without switching to the full feature pipeline.

Quick Start

Ask for a plan by writing: Describe what you want to implement for this task, then confirm the suggested mini-plan to run it step-by-step.

Frequently Asked Questions about quick-plan

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

FAQPage Schema
How do I create an executable plan for a medium-complexity coding task?▼

To create an executable plan for a medium-complexity coding task, you convert it into a 3–7 step inline mini-plan with atomic actions and explicit verification criteria before starting any work.

Does lightweight step-by-step execution work for small refactors and simple integrations?▼

Lightweight step-by-step execution works for small refactors and simple integrations by guiding one atomic step at a time with clear verification criteria, avoiding the overhead of full PRD pipelines.

What is the best way to apply TDD without switching to a full feature pipeline?▼

The best way to apply TDD without a full feature pipeline is generating a mini-plan that keeps tests-first behavior when applicable, requiring a final validation gate of tests and lint checks.

Can I generate a mini-plan without creating extra planning files on disk?▼

You can generate a mini-plan without creating extra files by producing the step and verify criteria inline directly within your current session, eliminating heavyweight planning artifacts on disk.

When should I avoid using mini-planning for development tasks?▼

You should avoid mini-planning for tasks requiring full PRD or heavy plan-feature pipelines, as it is specifically designed for medium-complexity work like incremental endpoint or validation tasks.

Related Skills

Explore More Software Engineering Skills→
yanun0323yanun0323
1

cmd-plan

Create a decision-ready coding plan with risk-based TDD guidance.

Community
Intermediate
prime-radiant-incprime-radiant-inc
91

verification-before-completion

Verify build, test, and lint results with evidence before declaring completion.

Official
Intermediate
JotJuniorJotJunior
21

execute-task

Execute backlog tasks through a mandatory nine-step workflow.

Community
Advanced
way-platformway-platform
6

prd

Generate structured PRDs from feature prompts and save them to markdown files.

Official
Intermediate