AGENT SKILL

fill-in-prototype

Complete a coherent presentation from a prototype and selected research evidence, composing writers for supported material and targeted prove/refute attempts for genuine gaps. Use for "fill in the prototype", "complete this exposition", or narrowly "work these conjectures". Requires doubt before promotion and returns actual artifacts and unresolved obligations to the synthesis coordinator; a fill request authorizes execution, not just recommendations.

License 许可
GPL-3.0
最近更新
2026-11-13
Stars
★ 0
Forks
0

01 前言 Front Matter

name
fill-in-prototype
description
Complete a coherent presentation from a prototype and selected research evidence, composing writers for supported material and targeted prove/refute attempts for genuine gaps. Use for "fill in the prototype", "complete this exposition", or narrowly "work these conjectures". Requires doubt before promotion and returns actual artifacts and unresolved obligations to the synthesis coordinator; a fill request authorizes execution, not just recommendations.

03 SKILL.md 正文

fill-in-prototype

The synthesis contract owns the end-to-end stages, reviews and integration. This leaf executes the requested fill, then returns to that coordinator. A direct request to work named conjectures stays confined to those items; a request to fill the presentation includes its definitions, proofs, examples and explanatory prose.

Fill from evidence, then resolve gaps

  1. Read the prototype, spec, selected originals and relevant live text; reconcile touched rows under LEDGER.md. Resolve audience, depth and target through RESOLUTION.md. Inventory missing content and genuine research obligations separately, with source locators and dependencies; report their counts. If the spec or structure is missing, compose create-exposition or rapid-prototype and the applicable outline review within the fill scope.
  2. Fill supported material in dependency order from the actual arguments, not the dump's status labels. Complete the topic introduction, definitions, statements, required proofs, worked examples and connective explanation to the audience's declared level. Preserve hypotheses, computational range, qualifications and counterexamples. Verify imported results through track-down-reference; a source citation does not replace a required self-contained proof.
  3. Resolve undetermined mathematics through using-mathpowers under the shared execution contract: supply exact statement, prerequisites and selected evidence; execute and consume attempts. Its backend/path preflight, delegation limits, persistent allowance, deadlines and loud failure gate govern every retry/review. Preserve packages, partial proofs, reductions and failed expectations; update spec/ledger links without silently expanding selection.
  4. Apply that contract's conflict investigation/adoption gate through contradiction-check; never silently replace an earlier claim. Run doubt before promotion and collect its verdict while independent work continues. Only SOUND on the actual statement/argument/dependencies satisfies the gate; changed evidence needs renewed scrutiny. WEAK, SUSPECT or absent verdicts block affected promotion, including computational or negative claims.
  5. Compose write-definition, write-proposition, write-example and write-remark for their respective content; use explain-experiment for computational exposition when needed. Supply each writer its evidence, prerequisites and concrete planned location. Produce the complete content, not a list of recommended writer calls. Scratch workers apply the writers' content disciplines and return candidate text/evidence only: no canonical mutation or canonical postamble during drafting. Reasonable reordering and insertion within the selected target are authorized unless a repository rule reserves them; retain relocations and recheck dependencies. Claims inside explanatory prose still require the proposition gates.
  6. Keep pre-integration candidates in permitted scratch Markdown, including LaTeX excerpts where useful; do not invent an undeclared .tex target. At requested integration, follow the manuscript-return gate, including its partial-stub restriction. The coordinator invokes WRITERS.md and the composed leaves in full at the declared canonical/aspirational destination. Preserve human markers and tagged history; keep statuses in the ledger. Drafting an introduction to the topic does not invoke or bypass write-introduction's finished-paper/abstract gates.
  7. Assemble the returns into one readable presentation, checking notation, transitions, labels and dependency coverage. Carry negative findings as substantive results with the expectation they correct (LX11/LX12); count those carried and exclusions with authorized reasons. Missing proofs stay explicit questions/conjectures, never theorem/proof placeholders presented as completed mathematics. Identify any unmet presentation requirement.

Return and continue

Return the exact candidate/edited regions, source and relocation map, evidence and doubt records, writer checks, and unresolved obligations with their blocked dependents. The coordinator consumes these artifacts and continues the shared presentation review/integration sequence; a writer's return is not a reason to end the synthesis. For direct fill requests, the invoking agent carries out the applicable review and requested delivery from that contract. Report actual completion or incompleteness. Source-candidate acceptance is not final manuscript acceptance: the coordinator must obtain the shared contract's final independent review of the integrated diff, its interfaces/dependency closure and compiled PDF. Neither outline acceptance nor a successful compile establishes a proof.

04 同仓库更多 Skills