hrt-adversarial-authoring

Cross-context adversarial authoring: one subagent drafts, two further subagents — each with no memory of the author's reasoning, only the inputs they were given — challenge the draft from two orthogonal angles before it's accepted.

This skill is shared by two callers. The calling instruction MUST state which artifact is being authored — that choice fixes the draft content, both review checklists, and the resolution target below. Nothing else about the process changes between callers.

Parameters (set by the caller)

• artifact: specs or design. (proposal is not reviewed here: its grounding is the user's own interview answers, and it is checked by hrt-artifact-lint plus the user's read-and-confirm.)
• content_sections: the sections the draft subagent must produce.
  • specs: one spec file per capability listed in the proposal's Capabilities section — ### Requirement blocks with #### Scenario WHEN/THEN content, per the specs phase's format rules.
  • design: Context, Goals/Non-Goals, Decisions, Shape / Seams (when the change adds callable code), Risks/Trade-offs, Migration Plan, Open Questions, per the design phase's format rules.
• grounding_inputs: the artifacts the draft subagent may read.
  • specs: proposal.md, existing specs in openspec/specs/ (for capability naming).
  • design: proposal.md, specs/**/*.md.

Process