vibe-add-feature
Skill7 starsChanged 13 days agoNo licenceView on GitHub
Full spec-driven workflow for adding a feature to an existing codebase with an AI coding agent. Triggers on "feature:" prefix, "I want to add a feature", "add X to my project", "new feature", "build a feature for". Always use when adding functionality to an existing project — even without the exact prefix. Reads PLAN.md feature map before drafting (when the project has one): checks build order, dependencies, shared data. Stops and surfaces clearly if dependencies are not yet met. Marks unplanned features explicitly. Updates PLAN.md feature map after the reviews so it stays the live source of truth. Creates vibe/features/[date-slug]/ with FEATURE_SPEC.md, FEATURE_PLAN.md, FEATURE_TASKS.md. Spec and plan are reviewed independently and approved before tasks are written; tasks are reviewed before the build. Checks for an incomplete feature with the same name first. Reads SPEC.md before drafting to align with existing acceptance criteria. Updates TASKS.md (human progress view) and agent files.
In this repository26 other files it gives its agents.
- vibe-agentSkill
- vibe-architectSkill
- vibe-brainstormSkill
- vibe-changelogSkill
- vibe-change-specSkill
- vibe-costSkill
- vibe-deploySkill
- vibe-design-mdSkill
- vibe-designSkill
- vibe-doctorSkill
- vibe-documentSkill
- vibe-e2eSkill
- vibe-fix-bugSkill
- vibe-goldfishSkill
- vibe-graphSkill
- vibe-handoffSkill
- vibe-initSkill
- vibe-ledgerSkill
- vibe-modeSkill
- vibe-new-appSkill
- vibe-parallelSkill
- vibe-perfSkill
- vibe-progressSkill
- vibe-reviewSkill
- vibe-spec-reviewSkill
- vibe-testSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
41 rules. About 0 are common, 17 are distinctive, and 24 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈17
Distinctive · estimate
This author's own choices. Worth a look.
24
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.