find-work

Files (1)

• SKILL.md

SKILL.md (first lines)

# Find Work

## Available tasks

Here are a set of GitHub issues:

!`gh issue list --state open --label agent:implement --json number,title,comments`

If there are no more tasks left, output <promise>NO MORE TASKS</promise>.

## Task selection

Pick the next task. Prioritize tasks in this order:

1. Critical bugfixes
2. Development infrastructure

Getting development infrastructure like tests and types and dev scripts ready is
an important precursor to building features.

3. Tracer bullets for new features

Tracer bullets are small slices of functionality that go through all layers of
the system, allowing you to test and validate your approach early. This helps in
identifying potential issues and ensures that the overall architecture is sound
before investing significant time in development.

TL;DR - build a tiny, end-to-end slice of the feature first, then expand it out.

4. Polish and quick wins
5. Refactors

## Implementation

Implement it using the `do-work` skill.

From tregusti/skills, MIT.

More from tregusti/skills