continuation-proposal

To automate task selection after a successful run, this Skill reads task_context.json, execution logs, and the task summary to propose the single highest-value continuation. It appends a scoped proposal object with title, summary, and a taskCreateRequest directly to the proposals JSON.

The best way to generate a continuation proposal for post-run orchestration is to analyze execution logs and task summaries. This identifies a concrete, implementation-ready next phase, refactor, or feature extension while avoiding duplicate titles in the proposals JSON.

To avoid duplicate task proposals when automating next-step recommendations, the proposal generation process checks existing proposals. It reads the run context and summary to append only a single, uniquely titled highest-value continuation task to the proposals JSON.

Yes, you can automatically enqueue a refactor or performance improvement after a successful build. The Skill outputs a concrete taskCreateRequest within the proposal object, allowing the selected next phase to be enqueued directly into your task orchestration workflow.

To propose a high-value continuation task automatically, the required inputs are task_context.json, execution logs, and the task summary. These artifacts provide the run context needed to determine and scope the next implementation-ready phase.

Yes, the proposed continuation task includes metadata for run-quality tracking. Proposals are tagged with the category "run_quality" and incorporate approved tags and signal metadata when applicable to maintain consistent orchestration standards.