Back to Guide
BUILDING

Feature Builder

Structured workflow for implementing a new feature. Returns a plan, files list, commands, test steps, and rollback plan.

Slash Command

Type this directly in Cursor or Claude Code chat

/feature-builder [describe the feature you want]

Install This Skill

Copy this prompt and paste it into Cursor (Ctrl+I) or Claude Code. The AI will handle the installation.

Install the Feature Builder skill from this GitHub repo: https://github.com/IdkwhatImD0ing/hackathonstarterkit

Run this command in the terminal:
npx skills add IdkwhatImD0ing/hackathonstarterkit --skill feature-builder

Then confirm the installation when prompted.

Skill Content

feature-builder/SKILL.md
Feature Builder

Feature Builder

The user wants to implement a new feature. They have no coding background. Guide them through a structured, safe process.

Step 1: Understand the Feature

Ask the user to describe: - What the feature should do (in their own words) - Who will use it - What it should look like (screenshots, sketches, or descriptions are all fine)

If the description is vague, propose 2-3 concrete interpretations and ask which one is closest.

Step 2: Create the Plan

Generate a plan with exactly these sections:

  1. 1Goal: One sentence describing the feature
  2. 2Steps: 5-10 numbered steps, each with a single goal
  3. 3Files: List every file that will be created or changed
  4. 4Dependencies: Any new libraries needed (ask before installing)
  5. 5Commands: Copy-paste terminal commands to run
  6. 6Manual Test: Step-by-step instructions to verify the feature works
  7. 7Rollback Plan: How to undo the changes if something breaks

Step 3: Implement

  • Build the smallest vertical slice first: input > minimal processing > visible output
  • Implement one step at a time; confirm each step works before moving to the next
  • Use the simplest libraries and hosted services available
  • Target a visible, working demo in under 60 minutes

Step 4: Verify

After implementation: - Run the project and capture any errors - Walk the user through the manual test steps - If errors occur, explain them in plain English and propose fixes - Ask: "Does this match what you had in mind?"

Constraints

  • Never add features the user did not ask for
  • Never make changes outside the scope of this feature
  • Keep changes minimal, testable, and reversible
  • Prefer high-level libraries over low-level implementations

Raw SKILL.md

Copy the full contents below and save as SKILL.md in a folder named feature-builder/.

---
name: feature-builder
description: "Structured workflow for implementing a new feature when you have no coding experience. Returns a plan, files list, commands, manual test steps, and rollback plan. Use when the user wants to add a feature to their project."
---

# Feature Builder

The user wants to implement a new feature. They have no coding background. Guide them through a structured, safe process.

## Step 1: Understand the Feature

Ask the user to describe:
- What the feature should do (in their own words)
- Who will use it
- What it should look like (screenshots, sketches, or descriptions are all fine)

If the description is vague, propose 2-3 concrete interpretations and ask which one is closest.

## Step 2: Create the Plan

Generate a plan with exactly these sections:

1. **Goal**: One sentence describing the feature
2. **Steps**: 5-10 numbered steps, each with a single goal
3. **Files**: List every file that will be created or changed
4. **Dependencies**: Any new libraries needed (ask before installing)
5. **Commands**: Copy-paste terminal commands to run
6. **Manual Test**: Step-by-step instructions to verify the feature works
7. **Rollback Plan**: How to undo the changes if something breaks

## Step 3: Implement

- Build the smallest vertical slice first: input > minimal processing > visible output
- Implement one step at a time; confirm each step works before moving to the next
- Use the simplest libraries and hosted services available
- Target a visible, working demo in under 60 minutes

## Step 4: Verify

After implementation:
- Run the project and capture any errors
- Walk the user through the manual test steps
- If errors occur, explain them in plain English and propose fixes
- Ask: "Does this match what you had in mind?"

## Constraints

- Never add features the user did not ask for
- Never make changes outside the scope of this feature
- Keep changes minimal, testable, and reversible
- Prefer high-level libraries over low-level implementations