fow_packet_author
Author bounded implementation packets in Flower MCP with complete instructions, stable plan units, dependencies, contracts, and checks; resolve engineering questions before execution.
Instructions
Define the bounded implementation work in a packet: complete instructions, stable plan units, dependencies, producer/consumer contracts and checks. Resolve engineering questions through ordinary authoring before execution. Route with operation: start_packet, revise_packet, replace_plan, resolve_questions, answer_gate, add_unit, revise_unit, remove_unit, rebind_unit, set_dependencies. Prerequisites: Use current specification/plan revisions and ordinary packet authority; investigate and close semantic gaps before dispatch. Effects: Creates/revises packets and complete ordered units/contracts/dependencies. Removal/replacement changes current plan authority; provider-target deltas may be queued, without executing coding work. Exact help (replace operation_name with the selected route): fow_capabilities({"view":"operation","operation_tool":"fow_packet_author","operation_name":"start_packet"}).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| unit | No | Complete bounded implementation-unit declaration, including instructions, targets, producer/consumer contracts and verification obligations as required by plan authority. Applies to: add_unit. Exact required/optional dotted fields and guidance: fow_capabilities(view=operation, operation_tool=fow_packet_author, operation_name=<selected route>). | |
| actor | Yes | Identity of the human or agent recording this action; retain the original identity when replaying its request. | |
| title | No | Short human-readable title of the authored requirement, finding, packet, run step or campaign. Applies to: start_packet, revise_packet. Required by: start_packet. | |
| intent | No | Engineering statement of the packet's intended observable behavior and authorized scope. Applies to: start_packet, revise_packet. Required by: start_packet. | |
| answers | No | Structured resolutions of the packet's currently open engineering questions, using their issued identities. Applies to: replace_plan, resolve_questions. Required by: resolve_questions. Exact required/optional dotted fields and guidance: fow_capabilities(view=operation, operation_tool=fow_packet_author, operation_name=<selected route>). | |
| purpose | No | Canonical packet purpose, including ordinary implementation or governed semantic remediation. Applies to: start_packet. Required by: start_packet. Canonical values: implementation, remediation. | implementation |
| goal_ids | No | Existing goal graph IDs governing the packet or campaign scope. Applies to: start_packet, revise_packet. | |
| in_scope | No | Behaviors and implementation boundaries explicitly included in this packet. Applies to: start_packet, revise_packet. | |
| response | No | Structured answer to the issued packet gate; use its current fingerprint and exact response contract. Applies to: answer_gate. Required by: answer_gate. Exact required/optional dotted fields and guidance: fow_capabilities(view=operation, operation_tool=fow_packet_author, operation_name=<selected route>). | |
| change_id | No | Canonical owning change ID; when address resolution permits omission, the packet/campaign must resolve unambiguously. | |
| operation | No | Operation selector for this multiplexer; use a canonical route listed below. Canonical values: start_packet, revise_packet, replace_plan, resolve_questions, answer_gate, add_unit, revise_unit, remove_unit, rebind_unit, set_dependencies. | add_unit |
| packet_id | No | Canonical packet identity returned by authoring; it identifies the bounded implementation work. | |
| rationale | No | Concrete reasoning supporting this ordinary mutation, decision or selected authority. Applies to: start_packet, revise_packet. | |
| work_plan | No | Complete ordered implementation plan with stable unit identities, dependencies, instructions and checks; accepted mutations give it authority. Applies to: replace_plan. Required by: replace_plan. Exact required/optional dotted fields and guidance: fow_capabilities(view=operation, operation_tool=fow_packet_author, operation_name=<selected route>). | |
| depends_on | No | Existing plan-unit identities this unit must consume before becoming executable. Applies to: set_dependencies. Required by: set_dependencies. | |
| invariants | No | Conditions that must remain true throughout the scoped behavior or change. Applies to: start_packet, revise_packet. | |
| project_id | Yes | Canonical lifecycle project ID. Select the existing project explicitly; development Markdown authorities are separate from runtime projects. | |
| request_id | Yes | Caller-owned retry identity. For receipted mutations replay the same actor and contents; changed contents can conflict. Inspect exact operation help for its receipt policy. | |
| unit_patch | No | Explicit patch to the identified existing plan unit; omitted fields preserve existing values under the ordinary revision rules. Applies to: revise_unit, rebind_unit. Required by: revise_unit, rebind_unit. Exact required/optional dotted fields and guidance: fow_capabilities(view=operation, operation_tool=fow_packet_author, operation_name=<selected route>). | |
| finding_ids | No | Existing assurance finding IDs that the corrective packet is intended to address. Applies to: start_packet. | |
| milestone_id | No | Existing milestone identity governing or filtering the requested scope. Applies to: start_packet. | |
| out_of_scope | No | Explicitly excluded behavior and implementation work for this packet. Applies to: start_packet, revise_packet. | |
| target_policy | No | Packet target-selection policy controlling explicit/provider/materialization readiness requirements. Applies to: start_packet. Canonical values: code_targets_required, documental_only. | code_targets_required |
| active_provider | No | Selected implementation-provider identity for provider-owned packet execution. Applies to: start_packet. | |
| client_unit_key | No | Stable caller-owned unit identity used to reconcile authoring retries and locate the intended plan unit. Applies to: add_unit, revise_unit, remove_unit, rebind_unit, set_dependencies. Required by: revise_unit, remove_unit, rebind_unit, set_dependencies. | |
| requirement_ids | No | Explicit existing requirement IDs defining the selected scope. Applies to: start_packet, revise_packet. | |
| source_revision | No | Declared repository/source revision associated with the work or evidence; does not independently prove implementation. Applies to: start_packet. | |
| gate_fingerprint | No | Fingerprint of the exact issued packet gate being answered; prevents responding to a different current gate. Applies to: answer_gate. Required by: answer_gate. | |
| target_selection | No | Structured existing navigation/plan-unit target selection; inspect its current identities before binding. Applies to: add_unit. | |
| architecture_refs | No | References to components, interfaces or decisions in one adopted architecture revision; omission preserves selection and [] explicitly clears it. Applies to: start_packet, revise_packet. | |
| completion_criteria | No | Ordered packet completion statements; these become stable criteria through the validation-authority workflow. Applies to: start_packet, revise_packet. Required by: start_packet. | |
| unresolved_questions | No | Known unresolved engineering/behavior questions retained on this packet; closure gates require resolution rather than anticipatory coding. Applies to: start_packet, revise_packet. | |
| predecessor_packet_id | No | Existing packet being superseded or corrected by this new packet. Applies to: start_packet. | |
| required_campaign_ids | No | Existing campaigns whose successful verification remains required by this corrective packet/finding. Applies to: start_packet. | |
| expected_plan_revision | No | Plan revision issued with the work or gate being acted on; do not replace stale issued authority to legitimize old work. Applies to: revise_packet, replace_plan, resolve_questions, answer_gate, add_unit, revise_unit, remove_unit, rebind_unit, set_dependencies. Required by: revise_unit, remove_unit, rebind_unit, set_dependencies. | |
| expected_spec_revision | No | Packet specification revision issued with the work or gate being acted on; mismatch rejects stale mutation. Applies to: revise_packet, replace_plan, resolve_questions, answer_gate, add_unit, revise_unit, remove_unit, rebind_unit, set_dependencies. | |
| required_regression_evidence | No | Declared regression evidence obligations that must remain visible until actually satisfied. Applies to: start_packet. | |
| predecessor_dependency_policy | No | Declared dependency treatment when creating a successor/remediation packet. Applies to: start_packet. Canonical values: materialized, context_only. | materialized |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||