repo-append-request-skill

To route repo append requests safely, classify them as append-feature, append-design, or append-milestone to produce an explicit routing decision. This prevents ambiguous requests from silently expanding scope or mutating control state.

Approval-aware routing for scope expansion evaluates repo goals and control state to output a structured routing result. It includes recommended next routes and explicit approval boundaries when authority is required for milestone creation.

Classifying design-only versus design-then-implementation paths involves categorizing append-design requests based on repo snapshot and control state. The routing output directs the harness to either isolate design steps or proceed to implementation.

No, you cannot create worktrack contracts directly during RepoScope intake. The routing logic must return a blocked status if it attempts to alter worktrack contracts or execute any side-effectful behaviors.

Append-feature requests get blocked during routing when the classification logic attempts to mutate milestones, write artifacts, or alter control state. The system enforces hard guardrails by only returning routing information without side effects.

You need explicit approval boundaries for repo governance requests when inputs require goal-change control, milestone creation, or scope expansion. The routing result identifies these boundaries to ensure authority is validated before proceeding.