p1-spec-research-policy

Standardizing Phase 1 research workflows requires formalized criteria, structured interview protocols, and decision gates to ensure consistency across hardware design specs. This Skill enforces governance rules and generates traceable artifacts like io_definition.json and timing_constraints.json to structure analysis.

Phase 1 hardware design documentation requires specific artifacts including iron-requirements.json, open-requirements.json, io_definition.json, timing_constraints.json, and review templates. These standardized formats ensure traceability and satisfy functional documentation requirements during cross-team reviews.

Conducting structured interviews for Phase 1 hardware design analysis involves applying predefined protocols and decision gates to guide stakeholder discussions. This approach resolves ambiguities early through governance and escalation workflows, ensuring all functional requirements are captured and reviewed.

Yes, aligning stakeholders on open requirements uses governance and escalation workflows defined by the Phase 1 research policy. It formalizes cross-team review protocols and generates open-requirements.json artifacts to systematically document and resolve ambiguities in hardware specs.

Generating iron-requirements and io_definition templates is best handled by running a standardized Phase 1 research workflow that outputs predefined JSON artifacts. This enforces naming conventions and checklist criteria to structure hardware design specifications consistently.

Hardware design specs lack traceability during Phase 1 research when artifact formats and review protocols are inconsistently scoped. Implementing formal governance rules, decision gates, and standardized templates like timing_constraints.json ensures consistent documentation and cross-team alignment.