Skip to content

docs: add 'When NOT to Use' section to vibe-start-informed #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ash1794 merged 1 commit into from
Jun 2, 2026
Merged

docs: add 'When NOT to Use' section to vibe-start-informed #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions plugins/vibe-engineering/skills/vibe-start-informed/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,13 @@ Other people's documented failures count as observed failure. Research SOTA befo

**Not for:** Implementing already-designed specs, bug fixes, or tasks with clear requirements.

## When NOT to Use

- Implementing an already-designed spec with clear requirements
- Bug fixes where the approach is already known
- Routine/mechanical changes with one obvious correct solution
- When the design decision has already been researched and recorded

## The Rule

**BEFORE proposing any approach, dispatch a research agent** to find real papers, real projects, and real production systems that solve the same (or adjacent) problem.
Expand Down
Loading