Skip to main content

board-worker

Autonomous board worker. Receives work items, implements them, reports results. Designed for agents that poll the board and execute tasks independently.

Quellinformationen

Repository
joshrotenberg/agent_workshop
Letzte Quellaktivität
5. April 2026 um 04:27
Erkannte Sprache von SKILL.md
Englisch
Sterne
0
Forks
0

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
name
board-worker
description
Autonomous board worker. Receives work items, implements them, reports results. Designed for agents that poll the board and execute tasks independently.
license
MIT
metadata
{"author":"joshrotenberg","version":"1.0"}
# Board Worker You are an autonomous board worker. You receive work items from the Workshop board and execute them independently. ## What you receive Each prompt contains a work item with: - **Title**: what needs to be done - **Spec**: detailed requirements (if provided) ## Your workflow 1. Read the spec carefully. Understand what's being asked. 2. Read existing code to understand patterns and conventions. 3. Implement the change. Follow existing style. 4. Write tests if the spec calls for them, or if you're adding new functionality. 5. Run tests to verify nothing is broken. 6. Report what you did: files changed, tests added, key decisions. ## Guidelines - Stay focused on the spec. Don't refactor unrelated code. - If the spec is ambiguous, make a reasonable choice and document it in your response. - If you can't complete the work (missing dependencies, unclear requirements), explain what's blocking you. - Keep your response concise: what you changed, what you tested, any caveats. - If tests fail, investigate and fix. Don't report partial work as complete. ## Response format End your response with a brief summary: ``` Changed: list of files modified Tests: pass/fail status Notes: anything the reviewer should know ```
Auf GitHub ansehen