codex-harness-javascript: Skill for Codex

Frontend Delivery Workflow

This is a user-facing workflow entry point. Main is the runtime Orchestrator; this workflow does not contain specialist implementation knowledge.

Intent

Run continuously from the smallest valid workflow entry until acceptance, pause, or a real blocker. Do not stop merely because the Jira work graph was created.

Entry resolution

Main resolves the current entry before dispatching children:

• NEW: no valid Jira workflow exists for the requested work.
• RESUME: valid Jira work state exists and relevant requirements are unchanged.
• REPLAN: relevant requirements or approved architecture changed materially.
• PAUSE: the user explicitly asks to stop/pause active work.
• ACCEPTANCE: required executable work is complete and final acceptance is due.

Natural-language pause intent such as dừng lại, tạm dừng, để mai làm tiếp, or equivalent must route to PAUSE.

Main orchestration rule

Main owns workflow decisions and runtime transport:

• lifecycle and execution-intent resolution;
• dependency-ready work selection;
• specialist and internal-capability routing;
• native child-agent spawn/retry/interrupt/close/verification;
• write-scope leases and source-diff verification;
• cross-agent runtime-resource cleanup supervision;
• specialist result reconciliation;
• compact transient workflow state.

Scrum Master owns Jira schema discovery, work-graph creation/reconciliation, Jira reads required by its assigned operation, and all authorized durable Jira mutations. Durable product specialists with their own execution unit (currently Design and Coding) may independently read only the exact Jira keys allowlisted in the current issue-handoff; Test Plan/Testing remain Jira-independent.

Every Scrum Master dispatch in this workflow must use the operation-specific runtime profile defined by the Main orchestration contract in AGENTS.md. Do not pin or infer an alternate model/effort inside this workflow.

Continuous delivery