Comet Native

Native saves complete requirements, progress, and acceptance results in the project. The Agent works only on the phase specified by Runtime. After each action, read the latest continuation and follow it until the task is complete, a user decision is needed, or an external dependency blocks progress.

Required rules

• Continue confirmed implementation, document repairs, evidence reuse, and recovery. Pause for new decisions, authorization, or external information. Use current continuation commands, templates, and packages; correct inputs within the same task.
• Treat .comet/config.yaml, the current change, comet-state.yaml, and formal artifacts on disk as authoritative; chat memory is supplementary. Among formal workflow files, the Agent edits only the brief, complete target Specs, association delta.yaml, and children.yaml. Runtime owns state, check results, reports, locks, and transactions.
• Advance through the public comet native CLI on PATH; do not ask the user to run commands manually. If the command is unavailable, report an incomplete installation and stop. Consult comet native <command> --help for arguments.
• Create changes with the CLI; use returned paths and follow denial commands or targets before retrying. Custom and non-Comet writes stay neutral.
• The Builder submits code as the candidate implementation. Each iteration requires a new read-only Verifier to assess every acceptance item independently. Assessing every item does not mean rerunning every command: reuse Runtime check records that still match the current candidate and add only missing or invalidated checks. Failed, blocked, unexecuted, and timed-out work cannot count as passed.
• Run confirmation commands only after the user explicitly confirms the complete Shape, accepts the final result, or selects the relevant delivery option. Reuse confirmed scope and user choices saved by Runtime. Authorization for Archive, merge, push, PR creation, and workspace cleanup is not interchangeable.
• This Skill and Runtime provide the Native workflow without an external Skill dependency. The Agent chooses implementation methods that preserve confirmed requirements and constraints.

Start or resume

1. If the name is known, run comet native select <change-name> --json. When an active change exists, enter the returned workspace.projectRoot; select returns the same discovery and state information as status, so a separate status call is not needed. Otherwise run comet native status --json. Let Runtime locate the workspace; ask the user only when multiple workspaces match equally well.
2. If there is no matching active change, select isolation and create it using workspace selection, then enter preparation.projectRoot. If preparation fails, preserve any branches and directories already created and address the reported cause.
3. After entering the workspace and obtaining phase, retrieve context once using memory integration. Expand details only when needed, record actual use outcomes, handle Project Memory and Personal Memory separately at task completion, and call comet task --complete as specified there.