Compare commits

...

2 Commits

Author SHA1 Message Date
Loic Duong 1807b2a8a4 docs: update planning workflow diagram 2026-06-05 12:43:13 +07:00
Alex Verkhovsky c9d9316e97
fix: clarify quick dev subagent use (#2450)
* fix: clarify quick dev subagent use

* fix: clarify subagent use in more workflows
2026-06-04 04:49:40 -07:00
4 changed files with 12 additions and 3 deletions

View File

@ -9,6 +9,9 @@ description: 'Review code changes adversarially using parallel review layers (Bl
**Your Role:** You are an elite code reviewer. You gather context, launch parallel adversarial reviews, triage findings with precision, and present actionable results. No noise, no filler.
Subagents, when the capability is available, are an important part of this workflow. Use them as directed by the workflow steps.
If you need an explicit user instruction to run them, ask once now for the whole workflow run.
## Conventions
- Bare paths (e.g. `checklist.md`) resolve from the skill root.

View File

@ -16,6 +16,9 @@ description: 'Creates a dedicated story file with all the context the agent will
- SAVE QUESTIONS: If you think of questions or clarifications during analysis, save them for the end after the complete story is written
- ZERO USER INTERVENTION: Process should be fully automated except for initial epic/story selection or missing documents
Subagents, when the capability is available, are an important part of this workflow. Use them as directed by the workflow steps.
If you need an explicit user instruction to run them, ask once now for the whole workflow run.
## Conventions
- Bare paths (e.g. `discover-inputs.md`) resolve from the skill root.

View File

@ -9,6 +9,9 @@ description: 'Implements any user intent, requirement, story, bug fix or change
**CRITICAL:** If a step says "read fully and follow step-XX", you read and follow step-XX. No exceptions.
Subagents, when the capability is available, are an important part of this workflow. Use them as directed by the workflow steps.
If you need an explicit user instruction to run them, ask once now for the whole workflow run.
## READY FOR DEVELOPMENT STANDARD
A specification is "Ready for Development" when:

View File

@ -202,19 +202,19 @@
<span class="workflow-name">prd</span>
</div>
<div class="workflow-meta">
<div class="agent"><div class="agent-icon john">J</div><span class="agent-name">Any</span></div>
<div class="agent"><div class="agent-icon john">J</div><span class="agent-name">John</span></div>
<span class="output">prd.md →</span>
</div>
</div>
<div class="decision">Has UI?</div>
<div class="workflow">
<div class="workflow-header">
<span class="workflow-name">create-ux-design</span>
<span class="workflow-name">ux</span>
<span class="badge iffy">if yes</span>
</div>
<div class="workflow-meta">
<div class="agent"><div class="agent-icon sally">S</div><span class="agent-name">Sally</span></div>
<span class="output">ux-spec.md →</span>
<span class="output">DESIGN.md + EXPERIENCE.md →</span>
</div>
</div>
</div>