repo-append-request-skill

What problem does it solve?

It prevents ambiguous “add this next” requests from silently expanding scope or mutating control state by classifying append-feature / append-design / append-milestone inputs into an explicit, approval-aware routing decision.

Core Features & Use Cases

• Append request intake & classification: Categorizes incoming requests into goal change, new milestone, new worktrack, scope expansion, design-only, or design-then-implementation based on repo goal, snapshot/status, and control state.
• Approval-aware routing output: Produces a structured Append Request routing result with recommended_next_route/scope and explicit approval boundaries when authority is required.
• Hard guardrails against side effects: Only returns routing information and must return blocked if the logic attempts to create/activate milestones, write artifacts, alter worktrack contracts, or execute design/implementation steps.

Quick Start

Ask your AI agent to classify and route the user’s追加请求 in mode append-feature (or append-design / append-milestone) by returning an Append Request routing result that includes the correct recommended_next_route and approval boundaries.