undefined

- Determine if target is an agent or skill based on which path exists
- Read target file to understand current state, capture line count
- If target does not exist in either location, stop and report error

**Step 3: Validate source material**

```markdown

- Read source file, confirm it is non-empty
- Estimate word count. If over 5,000 words, warn about elevated token cost.
- If material fails 2+ quality indicators, recommend inline analysis instead and ask user to confirm

**Step 4: Estimate token budget**

| Component | Estimated Tokens |
|-----------|-----------------|
| 10 agents x source material | source_words x 10 x ~3 |
| 10 agent outputs | ~5,000 (500 words each) |
| Synthesis | ~3,000 |
| Application | ~5,000 |
| **Total** | **sum of above** |

If total exceeds 60,000 tokens, warn user and request confirmation before proceeding.

**Gate**: Target exists and is readable. Source material is present and substantive. Token estimate is acceptable. Proceed only when gate passes.

Agent running > 5 minutes?
    |
    +-- YES --> Check progress (non-blocking)
    |           |
    |           +-- Making progress? --> Wait 2 more minutes
    |           |
    |           +-- Stuck on web fetch? --> Mark as timed out, proceed
    |
    +-- NO --> Continue waiting

| Rule | Struct | Clarity | Tech | Audience | Evidence | Narrative | Para | Header | Complex | Nuance | Count |
|------|--------|---------|------|----------|----------|-----------|------|--------|---------|--------|-------|
| [Rule A] | X | X | | X | | X | | | X | | 5 |
| [Rule B] | | | X | | X | | X | X | | X | 4 |

undefined

**Step 5: Save synthesis document**
- Write to `skills/do-parallel/artifacts/synthesis-{target}-{date}.md`
- Include the cross-reference matrix, themes, and prioritized rules
- This artifact persists for future reference and can inform later analyses

**Gate**: Synthesis document exists with at least 3 Must-Have and 3 Should-Have rules. Proceed only when gate passes.

undefined

**Step 2: Plan application**

Map each Priority 1 and Priority 2 rule to a specific location in the target:

```markdown

**Step 3: Apply Priority 1 rules**
- Add or enhance sections based on Must-Have recommendations
- Preserve all existing working patterns
- After each rule application, verify target file is still valid markdown

**Step 4: Apply Priority 2 rules**
- Add Should-Have enhancements where they integrate naturally
- Do NOT force rules that conflict with existing patterns
- If a Should-Have rule conflicts with an existing pattern, document the conflict in the report and skip

**Step 5: Commit changes**
- Create descriptive git commit explaining what was improved and from what source
- Bump version if target is a skill (e.g., 1.0.0 to 1.1.0)

**Gate**: Target file has been modified. Changes preserve existing behavior. Before/after diff shows additions only (no deletions of existing content). Proceed only when gate passes.

undefined

If any check fails, revert the problematic change and re-apply.

**Step 2: Generate completion report**

Use template from `references/perspective-prompts.md`. The report MUST include:
- Per-perspective key insights (one sentence each)
- Cross-reference showing which perspectives contributed to each improvement
- Before/after comparison (line counts, section counts)
- Estimated token usage breakdown
- Recommendations for future improvements

**Step 3: Save completion report**
- Write to `skills/do-parallel/artifacts/report-{target}-{date}.md`
- Present summary to user in conversation

**Step 4: Present results**

```markdown

**Gate**: Completion report exists. Target file is valid. All phases documented.

---

Estimated tokens = (source_words * 3 * 10) + 15,000

Example: 2,000-word article
  = (2,000 * 3 * 10) + 15,000
  = 60,000 + 15,000
  = ~75,000 tokens (HIGH - consider trimming source or reducing perspectives)

Example: 800-word article
  = (800 * 3 * 10) + 15,000
  = 24,000 + 15,000
  = ~39,000 tokens (ACCEPTABLE)