do-work

Files (2)

• QA.md
• SKILL.md

SKILL.md (first lines)

# Do Work

This skill should describe all meta stuff around one specific task. Adding or
removing labels on issues, commiting, pushing.

## Definitions

- **PRD**: Product Requirement Document, an issue that might exist. If so, it's
  a parent issue to some traces bullet slice "task issues".
- **Task issue**: The issue that contains the Issue Spec.
- **QA issue**: The issue created with the QA steps for a human to verify the
  implementation
- **Issue spec**: The issue description and any comments on the issue that
  clarify the requirements or constraints. This is the source of truth for what
  needs to be implemented. It may be in the form of an Agent Brief or a more
  traditional issue description.
- **Agent Brief**: A structured format for specifying work to be done, used by
  AFK agents. An Agent Brief is a type of issue spec, but not all issue specs
  are Agent Briefs. It is defined in the skill `triage`.

## Workflow

1. If github issue:
   - remove label `agent:implement`
   - add label `agent:in-progress`
2. Implement the issue spec using the `implement` skill.
3. Create a new QA issue using the `QA.md` template in this skill directory and
   add the `human:qa` label. If the task issue is part of a PRD, make the QA
   issue a _sub-issue_ to the PRD.
4. Commit the changes.
5. Push to remote.
6. If github issue, remove label `agent:in-progress`.

## Rules

1. Only work on one task/issue at a time!
2. Do not explicitly close any issues on github. Only implicitly by referencing
   them in commit messages and PRs.

From tregusti/skills, MIT.

More from tregusti/skills