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.

소스 정보

저장소
joshrotenberg/agent_workshop
최근 소스 활동
2026년 4월 5일 04:27
감지된 SKILL.md 언어
영어
스타
0
포크
0

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
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 ```
GitHub에서 보기