source-plan-authoringlisted

Retired compatibility pointer for users who explicitly invoke /source-plan-authoring or request the former standalone Source Plan stage. Direct long deliveries to /long-task-workflow, where raw or revised proposals, selected design resources and mixed attachments enter one Source-bound Contract Draft loop immediately. Do not create a legacy standalone Source Plan or internal Source-authoring stage, gate, schema, state or second plan.
Seven128/project-tiny-context-harness · ★ 3 · API & Backend · score 67

Install: claude install-skill Seven128/project-tiny-context-harness

# Retired: Source Plan Authoring `/source-plan-authoring` no longer defines a separate handoff between the initial proposal and Long-Task execution. For an explicit long delivery, invoke `/long-task-workflow` with the initial/revised proposal, selected immutable design resources and other attachments. They enter the same `delivery-contract.yaml` Draft immediately; input inventory, Source-quality synthesis/refinement, stable semantic keys, control-level UI meaning, acceptance scenarios, research/delegation traceability, real Source marking, repository binding and Contract mapping converge in one Goal before Preflight/Compile. For non-long work, give the proposal and selected resources directly to the current native Goal under the default Workflow Contract. If the user only wants an initial product or technical proposal, use the applicable proposal-authoring capability rather than recreating this retired intermediary. A pre-existing Source Plan remains valid ordinary Source. Do not rewrite it merely for compatibility, create a new Source Plan artifact, invoke Long-Task automatically, or create a second plan, Contract Draft, Preflight, Compile, Receipt, Authority or state surface from this pointer.