feature-quick

Implement small code changes with TDD and minimal setup.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/telefrek/jlsm --skill feature-quick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-quick
Source: https://github.com/telefrek/jlsm/tree/main/.claude/skills/feature-quick
Command: npx skills add https://github.com/telefrek/jlsm --skill feature-quick

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enables quick implementation of well-understood changes that require minimal setup, streamlining the process for developers who already know what needs to be built.

Core Features & Use Cases

  • Lightweight Entry Point: Perfect for small, single-construct changes that don't require extensive planning.
  • TDD Discipline: Adheres to test-driven development principles with minimal setup.
  • Scoping Interviews: Avoids unnecessary interviews and domain analysis for simple changes.
  • Use Case: When you need to add a simple feature or fix a bug that's clear-cut and doesn't require architectural decisions.

Quick Start

Start a new quick feature by running: `/feature-quick "<description>"

Frequently Asked Questions about feature-quick

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

FAQPage Schema
How do I implement small code changes quickly without extensive setup?

To implement small code changes quickly, use a lightweight entry point that skips scoping interviews and domain analysis. This approach streamlines development for well-understood modifications within a single construct and session.

Can I use test-driven development for quick bug fixes?

Yes, you can apply test-driven development for quick bug fixes. This method integrates TDD discipline with minimal setup, allowing you to write tests and implement clear-cut fixes efficiently without architectural overhead.

What is the best way to add a simple feature without architectural decisions?

The best way to add a simple feature without architectural decisions is using a focused implementation approach. It operates within a single construct, adheres to TDD principles, and performs a pre-flight complexity assessment to ensure the change remains lightweight.

When should I avoid using a quick implementation approach for code changes?

You should avoid using quick implementation when a code change is not well-understood, requires significant architectural decisions, or extends beyond a single construct and session. This method is strictly for lightweight, clear-cut modifications.

Does minimal setup code implementation work with complex project configurations?

Minimal setup code implementation requires existing project configuration to function. It operates within the constraints of your current environment, making it suitable only when the project is already configured for the targeted single-construct changes.