AX Engineering Console

skill / plan-feature

Plan feature

Experimental

Turn findings into an ordered, bounded plan whose scope, verification, and approval points are explicit before implementation starts.

Prerequisites

  • Investigation findings for the requirement.
  • Knowledge of which quality gates the project enables.

Steps

  1. State the scope and, just as explicitly, the non-goals.
  2. List the layers and files each step will touch.
  3. Sequence the steps so that each one can be verified on its own.
  4. Attach the verification command or check to every step.
  5. Mark the points where a human must approve before continuing.
  6. Confirm no step needs a capability the role does not hold.

Capabilities needed

  • read_code
  • read_docs

Outputs

  • An ordered plan naming files and verification for each step.
  • Explicit non-goals that keep unrelated refactoring out of scope.
  • The approval points a human must clear.

Verification

  • Each step names what it changes and how it is checked.
  • The plan excludes cleanups the requirement did not ask for.

Escalates when

  • The plan cannot work without a denied capability.
  • The requirement turns out to be larger than the requester expects.
skill / plan-feature
{
  "schemaVersion": 1,
  "id": "plan-feature",
  "name": "Plan feature",
  "status": "experimental",
  "purpose": "Turn findings into an ordered, bounded plan whose scope, verification, and approval points are explicit before implementation starts.",
  "prerequisites": [
    "Investigation findings for the requirement.",
    "Knowledge of which quality gates the project enables."
  ],
  "steps": [
    "State the scope and, just as explicitly, the non-goals.",
    "List the layers and files each step will touch.",
    "Sequence the steps so that each one can be verified on its own.",
    "Attach the verification command or check to every step.",
    "Mark the points where a human must approve before continuing.",
    "Confirm no step needs a capability the role does not hold."
  ],
  "capabilities": [
    "read_code",
    "read_docs"
  ],
  "outputs": [
    "An ordered plan naming files and verification for each step.",
    "Explicit non-goals that keep unrelated refactoring out of scope.",
    "The approval points a human must clear."
  ],
  "verification": [
    "Each step names what it changes and how it is checked.",
    "The plan excludes cleanups the requirement did not ask for."
  ],
  "escalation": [
    "The plan cannot work without a denied capability.",
    "The requirement turns out to be larger than the requester expects."
  ]
}

Rendered from the loaded definition rather than read from disk, so there is no file path for a request to influence.