[shinpr]

Problem

• The orchestration guide told the orchestrator to compose specialist inputs, extract facts, and pass only selected analyzer material. Review Resolution passed only the orchestrator's selected response to the author. In practice, the orchestrator restated sources and added constraints, reading lists, and product assumptions the user had not chosen. A specialist reads that text as a requirement, although no user confirmed it and no reviewer checked it. It drifts from the source and changes scope without a decision.
• The Design Doc template asked for Current requirements without saying whose words. The designer wrote requirements in its own words, sometimes merging its interpretation into a requirement, and planning and implementation then treated that interpretation as the user's requirement.

Changes

• subagent-delegation: pass each source (user words, governing artifact, review finding, another agent's result) by its path or copied unchanged, and label the parent's own decisions. The skill states why this takes precedence over writing a delegation prompt out in full, and routes a gap in a source to the owner of that decision.
• subagents-orchestration-guide: the orchestrator fills specialist input contracts and recipe slots from their sources; analyzer and other result fields are passed unchanged.
• review-resolution and the update mode of both designers: findings are passed as returned, with the orchestrator's disposition labeled; the author derives the edit from the finding and the governing sources.
• design-template: requirements stay in their carrier's words; the design's reading of them goes in Selected Design.
• recipe-update-doc: the change request and clarification answers are passed as given.
• llm-friendly-context: a governing source is passed by path or unchanged excerpt.
• Bump the package version to 1.8.4.

Unchanged and checked for consistency: verbatim user wording when it exists only in conversation, the labeled working summary when no wording exists, orchestrator-owned decisions, the convergence record lifecycle, and the review recipes' correction steps.

Validation

• npm test passed.

🤖 Generated with Claude Code