Find agent skills by outcome

- ${feature} - Feature to be accessed (e.g.

posts

Ethreal Current

Experimental downtempo, complex breakbeat influenced by jazz, glitchy foley percussion, staccato cello stabs, soaring violin textures, sub-bass movements, vinyl crackle, and ambient nature sounds, cin...

- Point to likely files/modules: src/...

app/...

- Ensure the summary is clear and concise

maintaining the original meaning

- Vague steps (“handle backend”

“do auth”)

- Include safe rollout when relevant: feature flag

migration plan

- Name concrete validation: “Run npm test”

“Add unit tests for X”

<1–3 sentences: what we’re doing

why

- Identify constraints (language

frameworks

- If there are unknowns

include a tiny Open questions section (max 3).

- If unsure but not blocked

make a reasonable assumption and proceed.

- Each checklist item should be a concrete action and

when helpful

- Verb-first: “Add…”

“Refactor…”

Turn a user prompt into a single

actionable plan delivered in the final assistant message.

- Read README.md and any obvious docs (docs/

CONTRIBUTING.md

test('should pass after fix'

() => {

test('should handle edge cases'

() => {

OpenAI Create Plan Skill

describe('BUG-[ID]: [Bug description]'

() => {

test('should fail with original bug'

() => {

For EVERY fixed bug

provide:

- [ ] Fix addresses the root cause

not just symptoms

3. Implement minimal

focused fix

For each identified bug

document: