Multi-Agent Issue Implementation FAQs

Question 1

What happens if a code change is too small for its own PR?

Accepted Answer

The skill includes a bundling protocol where workers can request additional related issues to implement in the same branch if the initial changes are deemed too small to justify a standalone pull request.

Question 2

How are dependencies between issues managed?

Accepted Answer

The skill detects dependency ordering from issue bodies or native tracker metadata (like Gitea dependencies) to ensure that foundational tasks are completed before dependent tasks are assigned to workers.

Question 3

Can I use this skill without a specific specification document?

Accepted Answer

Yes, if no SPEC or issue number is provided, the skill will analyze your backlog, prioritize unblocked tasks, and propose a work plan for your approval.

Question 4

Does the skill run tests before creating a pull request?

Accepted Answer

By default, the skill executes existing tests within each worktree to ensure quality. You can skip this step using the --no-tests flag if desired.

Question 5

How does the Work skill handle multiple issues at once?

Accepted Answer

It uses Git worktrees to create separate directory environments for each issue, allowing multiple sub-agents to work on different branches simultaneously without interfering with your main working directory.

Multi-Agent Issue Implementation

주요 기능

사용 사례

Multi-Agent Issue Implementation

주요 기능

사용 사례