[QUALITY-635] Add required Parallelization section to write-tech-spec skill#10400
Merged
Conversation
Adds a required Parallelization section (#4) to the tech spec skill, modeled after the parallelism guidance in the server-side run_agents prompt. Tech specs now actively evaluate whether parallel sub-agents would reduce wall-clock time or isolate work, and document the strategy (agent roles, execution mode, worktrees, branch/PR strategy, and coordination boundaries). Co-Authored-By: Oz <oz-agent@warp.dev>
Contributor
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
szgupta
approved these changes
May 7, 2026
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Overview
This PR updates the write-tech-spec skill to make Parallelization a required section and expands the details specs should provide when sub-agents are proposed.
Concerns
- The new required section currently tells agents to skip it when
run_agentsis unavailable, which undermines the requirement to document the parallelization decision.
Verdict
Found: 0 critical, 1 important, 0 suggestions
Request changes
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
| Reference `PRODUCT.md` for user-visible behavior rather than restating it. | ||
| 2. **Proposed changes** — The implementation plan: which modules change, new types/APIs/state being introduced, data flow, ownership boundaries, and how the design follows existing patterns. Call out tradeoffs when there is more than one reasonable path. | ||
| 3. **Testing and validation** — How the implementation will be verified against the product behavior. Owns everything about proving the feature works: unit tests, integration tests, manual steps, screenshots, videos, and any other verification. Reference the numbered Behavior invariants from `PRODUCT.md` directly rather than restating them; each important invariant should map to a concrete test or verification step. This section is where validation lives — `PRODUCT.md` intentionally does not have a Validation section. | ||
| 4. **Parallelization** — Actively evaluate whether parallel sub-agents (launched via `run_agents`) would meaningfully reduce wall-clock time or isolate work. Skip this section if `run_agents` is not available. When the spec proposes using sub-agents, include for each proposed agent: |
Contributor
There was a problem hiding this comment.
run_agents, so specs can skip documenting why parallelization is unavailable; keep the section and record that reason instead.
Suggested change
| 4. **Parallelization** — Actively evaluate whether parallel sub-agents (launched via `run_agents`) would meaningfully reduce wall-clock time or isolate work. Skip this section if `run_agents` is not available. When the spec proposes using sub-agents, include for each proposed agent: | |
| 4. **Parallelization** — Actively evaluate whether parallel sub-agents (launched via `run_agents`, when available) would meaningfully reduce wall-clock time or isolate work. If `run_agents` is not available, keep this section and state that parallelization cannot be used in the current environment. When the spec proposes using sub-agents, include for each proposed agent: |
cephalonaut
changed the title
trungtai1805
pushed a commit
to trungtai1805/warp
that referenced
this pull request
May 9, 2026
…tdev#10400) ## Description Add a required Parallelization section (warpdotdev#4) to the `write-tech-spec` skill, modeled after the parallelism guidance in the server-side `run_agents` prompt. Tech specs now actively evaluate whether parallel sub-agents would reduce wall-clock time or isolate work, and document the strategy including agent roles, execution mode, worktrees, branch/PR strategy, and coordination boundaries. ## Linked Issue N/A — internal skill improvement. ## Testing Documentation-only change (skill markdown file). No code changes. ## Agent Mode - [x] Warp Agent Mode - This PR was created via Warp's AI Agent Mode Co-Authored-By: Oz <oz-agent@warp.dev> Co-authored-by: Oz <oz-agent@warp.dev>
1 task
tungd
pushed a commit
to tungd/warp
that referenced
this pull request
May 11, 2026
…tdev#10400) ## Description Add a required Parallelization section (warpdotdev#4) to the `write-tech-spec` skill, modeled after the parallelism guidance in the server-side `run_agents` prompt. Tech specs now actively evaluate whether parallel sub-agents would reduce wall-clock time or isolate work, and document the strategy including agent roles, execution mode, worktrees, branch/PR strategy, and coordination boundaries. ## Linked Issue N/A — internal skill improvement. ## Testing Documentation-only change (skill markdown file). No code changes. ## Agent Mode - [x] Warp Agent Mode - This PR was created via Warp's AI Agent Mode Co-Authored-By: Oz <oz-agent@warp.dev> Co-authored-by: Oz <oz-agent@warp.dev>
lawsmd
pushed a commit
to lawsmd/cortex
that referenced
this pull request
May 22, 2026
…tdev#10400) ## Description Add a required Parallelization section (warpdotdev#4) to the `write-tech-spec` skill, modeled after the parallelism guidance in the server-side `run_agents` prompt. Tech specs now actively evaluate whether parallel sub-agents would reduce wall-clock time or isolate work, and document the strategy including agent roles, execution mode, worktrees, branch/PR strategy, and coordination boundaries. ## Linked Issue N/A — internal skill improvement. ## Testing Documentation-only change (skill markdown file). No code changes. ## Agent Mode - [x] Warp Agent Mode - This PR was created via Warp's AI Agent Mode Co-Authored-By: Oz <oz-agent@warp.dev> Co-authored-by: Oz <oz-agent@warp.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Add a required Parallelization section (#4) to the
write-tech-specskill, modeled after the parallelism guidance in the server-siderun_agentsprompt. Tech specs now actively evaluate whether parallel sub-agents would reduce wall-clock time or isolate work, and document the strategy including agent roles, execution mode, worktrees, branch/PR strategy, and coordination boundaries.Linked Issue
N/A — internal skill improvement.
Testing
Documentation-only change (skill markdown file). No code changes.
Agent Mode
Co-Authored-By: Oz oz-agent@warp.dev