vibe-how-do-we-do

Solid

Design the approach and execution plan by entering the canonical vibe runtime with a planning-first bias.

AI & Automation 2,202 stars 164 forks Updated 1 weeks ago Apache-2.0

Install

View on GitHub

Quality Score: 89/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
39
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

Use canonical `vibe` as the only governed runtime authority for this request. Entry bias: - choose an approach - design execution structure - sequence the work before implementation - stop after canonical `xl_plan` Execution rules: - delegate to canonical `vibe` - keep `vibe` as the only runtime authority - do not create a second requirement surface - do not create a second plan surface - do not create a parallel runtime - do not continue into `plan_execute` or `phase_cleanup` unless the user explicitly re-enters through canonical `vibe` or another approved wrapper When this wrapper is chosen, enter canonical `vibe` with: - approach selection - explicit planning - stronger transition into `xl_plan` - a bounded terminal stage of `xl_plan` Request: $ARGUMENTS

Details

Author
foryourhealth111-pixel
Repository
foryourhealth111-pixel/Vibe-Skills
Created
3 months ago
Last Updated
1 weeks ago
Language
Python
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category