PBR Quick Task Execution FAQs

Question 1

How does the atomic commit feature work?

Accepted Answer

The executor subagent automatically formats git commits using the 'type(quick-NNN): description' pattern, where NNN is the auto-incremented task ID, making your git history easy to audit.

Question 2

What is the benefit of the --research flag?

Accepted Answer

The --research flag spawns a specialized researcher subagent to investigate codebase patterns and potential risks before the executor begins work, ensuring the 'quick' fix follows existing project conventions.

Question 3

When should I use the Quick skill instead of the full Plan skill?

Accepted Answer

Use the Quick skill for small, well-defined tasks that touch a limited number of files. If a task requires more than 3-5 subtasks or affects multiple major subsystems, the full /pbr:plan workflow is recommended.

Question 4

Does the Quick skill still track changes in my project state?

Accepted Answer

Yes. Even in zero-friction mode, the skill creates task directories in .planning/quick/, generates a SUMMARY.md, and updates your project's STATE.md to ensure all changes are documented.

Question 5

Can I use the Quick skill for critical fixes?

Accepted Answer

Yes. By using the --full flag, you enable plan-checker validation and post-execution verification, providing a safety net for important changes while still moving faster than the full planning cycle.

PBR Quick Task Execution

PBR Quick Task Execution

주요 기능

사용 사례

주요 기능

사용 사례