AGENT SKILL

author-spec

Create, adopt, or revise a specification or scoping document before decomposing work into briefs, including useful delivery milestones and their acceptance criteria. Use for requirements, system design, architecture proposals, and reviewing an existing spec for decision readiness. Use author-brief for execution decomposition.

License 许可
Apache-2.0
最近更新
2026-11-15
Stars
★ 7
Forks
5

01 前言 Front Matter

name
author-spec
description
Create, adopt, or revise a specification or scoping document before decomposing work into briefs, including useful delivery milestones and their acceptance criteria. Use for requirements, system design, architecture proposals, and reviewing an existing spec for decision readiness. Use author-brief for execution decomposition.

02 资源文件 2

03 SKILL.md 正文

Author Spec

Produce a sufficient, evidence-backed source of intent that downstream briefs can cite. Specify outcomes, boundaries and consequential decisions; leave execution scheduling to author-brief. This skill chooses no product architecture, taxonomy or technology for an adopter. Read applicable project guidance for preferred techniques and actual constraints; an absent local profile is valid. Do not turn a preference into a binding constraint.

Bind implementation pickup to current context

Read the implementation pickup procedure. Specs and briefs identify the selected target/transition, semantic contracts and applicable project engineering guidelines by canonical pointer. Include their pickup/resume assessment in the implementation handoff; record revisions, coverage and continue/adapt/hold rather than assume the authoring snapshot is still current. Use the shipped context operation where the installed version supports it (see the supported version below); otherwise use the explicit manual bootstrap. Do not rewrite completed Evidence or let a draft proposal veto approved work.

Hand changed planned work over as a context receipt

When a spec changes planned work (a contract, owner, transition or approved target that existing briefs consume), hand it to author-brief as a record, not prose alone:

  1. Write the target record (declaring brief, target state and revision, approval and contract changes) into the context snapshot the project assembles, then run statusgen context discover --snapshot DIR --json > receipt.json.
  2. The receipt is a context-handoff-v1 record (context-handoff-v2 when an impact is withdrawn, context-handoff-v3 when the snapshot carries product targets). Record each actionable impact's disposition and each amendment obligation in it. An impact left unresolved is an open question for the brief author, never a silent pass.
  3. Keep product and architecture bindings separate. A brief's outcome and outcome-revision bind it to a product target revision, and the receipt keeps the revision the work was first selected against when a brief rebinds. Never drop or rewrite that revision to make an assessment read aligned. A receipt without a product section covers architecture only and says product alignment is unchecked.
  4. Exit 3 is a hold: coverage is partial. Name the could-not-check sources in the handoff; never report the receipt complete.

Supported version. statusgen context discover, statusgen context recheck and statusgen context check, with the context-handoff-v1 and context-handoff-v2 receipts and the amendment-manifest-v1 file, ship in Assay v1.0.55 and later. The product-binding extension, context-handoff-v3, ships in v1.0.63 and later. statusgen context --help lists the verbs an install has.

Manual bootstrap. When the installed statusgen lacks the verb, or lacks the product-binding extension while briefs bind outcome-revision, follow the implementation pickup procedure by hand: record the impacted briefs, their revisions, coverage and each amendment obligation in the handoff, and say that it is a manual bootstrap. Never invent a receipt or a schema version the install does not ship.

Start from the controlling source

Find the existing spec, relevant decisions, affected consumers and current implementation. Choose create only when no sufficient source exists, adopt when an existing artifact already settles the needed questions, or revise for a bounded change to that source. Keep adequate formats and content. Adoption may need only citations and a short gap note; do not manufacture a parallel spec or reformat an approved one to satisfy this skill.

Pin material source revisions or dates. Distinguish observed behaviour, approved intent, proposals, assumptions and unresolved decisions. Inspect relevant code/tests for brownfield work; a completed brief or incident report alone is not evidence of current behaviour. Unavailable evidence stays explicit. Do not substitute absence of access for absence of a constraint. For a revision, preserve completed implementation and Evidence; identify which unfinished work and consumers the delta affects.

Consider available quality evidence for the affected area and relevant seams: complexity, change churn, coupling, recurring defects, test weaknesses and existing investigations or brittle marks. Record the source revision/window and its relevance to this change; stale or unavailable measurements remain gaps, not evidence of good quality. A metric nominates an area for investigation; a high score alone neither proves a defect nor mandates a rewrite. Use the project's instruments and thresholds without inventing universal cutoffs.

Choose a proportionate disposition: remediate first when safe delivery or verification depends on it; include a bounded improvement when it removes the mechanism this change would extend; route broader remediation separately with its dependency or independence made explicit; or proceed with a reason and residual risk when evidence does not justify expansion. Touching a file is not blanket authority to refactor it. For included work, name the expected improvement, behaviour to preserve, and an observable acceptance check. Judge safer delivery and reduced recurring complexity, not a lower score in isolation.

Capture delivery milestones

For stream scoping, staged delivery or a requested milestone revision, read the shared milestone authoring procedure, including its support check and Author-spec section. Capture useful outcomes as <cell>:<repo>:<stream>:m-<NN>; identify proposed briefs as <cell>:<repo>:<stream>:b-<NN> per brief §3.8, allowing :b-<NN>@<version> references and preserving legacy aliases and reader compatibility. Full record IDs include cell/repo; colon elisions use context. Capture supported scope, acceptance criteria/evidence and authority, versioned prerequisite capabilities and open decisions. Preserve existing promises; do not infer milestone order from wave numbers or decompose the execution work here. Carry these records into the brief-authoring handoff. While readers lack support, capture proposals in the scoping document rather than operational milestone YAML. When a useful outcome includes simulated or temporarily absent dependencies, apply the shared procedure's Outcomes delivered with simulated dependencies section. Capture real/substitute boundaries, evidence limits and real-service replacement requirements before decomposition; use existing scope and acceptance sections rather than a new universal spec template.

Resolve the consequential questions

Scale depth to uncertainty and impact: a small change may take a paragraph and examples; an architectural change needs the boundaries below; exploration may end in a bounded spike with an unanswered question and discriminating observation. These are questions to answer where relevant, not required headings or a section-count gate.

  • Outcome and scope. Whose problem is supported by what evidence? Name the workflow, success observable, exclusions and domain terms whose ambiguity changes behaviour.
  • Existing obligations. Identify inherited decisions and the semantic owner of each affected meaning. Link the canonical contract or record the gap. A theme, plane, substrate, directory or stream label does not confer ownership or authority. Surface a conflict with a controlling decision; do not silently override it in a local design.
  • Behaviour and boundaries. Describe inputs, outputs, states and relevant failure, recovery and partial-success paths. Identify producers and consumers across seams, the authority to act, and capabilities that must not cross a boundary, including transitively. Name reusable library/API entrypoints when they exist. Justify an additional process by a concrete isolation, custody, deployment or lifecycle need; do not assume every logical layer needs a service or that sharing code transfers authority to its callers. Check proposed reuse from the consumer's actual module/package and version boundary; code existing somewhere is not proof it is importable or compatible. If extraction is needed, identify its owner and the prerequisite before promising reuse.
  • Design and alternatives. Separate required outcomes from the proposed mechanism and incidental implementation choices. Record consequential alternatives and tradeoffs. For a recurring defect, identify the hypothesised mechanism and owning layer; consider removing the hazard or reusing its owner before adding another guard or exception. State what the proposal retires and what added complexity remains justified. Apply the project's existing design-fit procedure rather than creating another register or gate.
  • Quality attributes. Use the quality prompts to select material concerns, prioritize tradeoffs and express verifiable scenarios with conditions, targets, provenance and evidence owners. Reuse inherited obligations; unknown targets stay explicit. Identify costly paths and scaling risks before decomposition. Keep this proportionate: no mandatory category checklist or invented budgets.
  • Change and compatibility. Explain migration, version compatibility, affected callers, rollback or recovery, and retirement of the previous path where applicable. Distinguish the desired end state from a transition that intentionally carries two implementations.
  • Proof and decisions. Map conditions to independently verifiable acceptance examples, including a relevant failure or boundary case, and the evidence that could falsify the design. State what can be checked now versus after implementation. Separate facts from hypotheses; do not claim a metric or retrospective comparison proves causation. For each check that needs a database or another service, name the NON-PRODUCTION instance it runs against and what reaching it requires (network, a credential); briefs carry that name into the Verify table's Env column as service:<name>, and such a check is never hermetic CI. Name remaining decisions and their authorized owner, with options and a recommendation. Continue independent work while a decision is pending; do not silently choose on that owner's behalf.

Keep the minimum durable rationale needed to prevent independent implementers choosing incompatible meanings. Reuse existing decision records, contracts and evidence references. Use review prompts when a brownfield redesign or a spec-quality review needs a deeper check; do not load it for every small edit.

Review and hand off

Review coverage, contradictions and plausible counterexamples against actual sources. On revisions, include unchanged criteria, inherited constraints and accepted decisions. Report gaps with their source and consequence; formatting preferences are not defects. An adequate spec needs no change. Separate changed intent from implementation defects; do not weaken correct intent to fit a bug. Use the linked review prompts as needed.

Follow the existing spec lifecycle for Assay-tracked specs: draft, approved, routed; the ruling and citing briefs establish the transitions. A review by this skill grants no approval or implementation authority. When authorized to decompose, use author-brief, whose Context contract owns design-fit, layering and architectural-contract references. Carry the controlling source and unsettled obligations into briefs; do not duplicate that schema here or invent a second task/status system. If this task is only spec authoring, deliver the spec, its material open decisions and the next authorized step without auto-starting implementation.

04 同仓库更多 Skills

medici-finance
medici-finance/assay

Bad--Name

A valid description.

★ 7
medici-finance
medici-finance/assay

not-the-desk

A valid description.

★ 7
medici-finance
medici-finance/assay

skill

abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde

★ 7
medici-finance
medici-finance/assay

skill

字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字字 字字字字

★ 7
medici-finance
medici-finance/assay

skill-9

This is a filler sentence used only to push the summed bundle description character budget over its threshold for the fixture. This is a filler sentence used only to push the summed bundle description character budget over its threshold for the fixture. This is a filler sentence used only to push the summed bundle description character budget over its threshold for the fixture. This is a filler sentence used only to push the summed bundle description character budget over its threshold for the fixture. This is a filler sentence used only to push the summed bundle description character budget over its threshold for the fixture. This is a filler sentence used only to push the summed bundle description character budget over its threshold for the fixture. This is a filler sentence used only to push the summed bundle description character budget over its threshold for the fixture. This is a f

★ 7
medici-finance
medici-finance/assay

skill-8

This is a filler sentence used only to push the summed bundle description character budget over its threshold for the fixture. This is a filler sentence used only to push the summed bundle description character budget over its threshold for the fixture. This is a filler sentence used only to push the summed bundle description character budget over its threshold for the fixture. This is a filler sentence used only to push the summed bundle description character budget over its threshold for the fixture. This is a filler sentence used only to push the summed bundle description character budget over its threshold for the fixture. This is a filler sentence used only to push the summed bundle description character budget over its threshold for the fixture. This is a filler sentence used only to push the summed bundle description character budget over its threshold for the fixture. This is a f

★ 7