pub struct Wording {Show 16 fields
pub product: &'static str,
pub name: &'static str,
pub unit: &'static str,
pub intent_paths: &'static str,
pub intent_code: &'static str,
pub documents: &'static str,
pub authoring: &'static str,
pub authoring_tool: &'static str,
pub story: &'static str,
pub constitution: &'static str,
pub plan: &'static str,
pub plan_short: &'static str,
pub examples: &'static str,
pub convergence_task: &'static str,
pub files: [&'static str; 3],
pub assess: Assess,
}Expand description
Model-facing fragments; the prompts around them are the same for every format.
Fields§
§product: &'static strThe format as the model is told it, e.g. GitHub Spec Kit.
name: &'static strThe format’s short name, e.g. Spec Kit.
unit: &'static strWhat one unit of work is called, e.g. feature.
intent_paths: &'static strThe intent paths, e.g. .specify/, specs/.
intent_code: &'static strThe same as code spans.
documents: &'static strThe documents convergence reads, e.g. spec.md, plan.md and tasks.md.
What a planning skill may do, e.g. write Spec Kit artifacts (…) and run Spec Kit's own scripts under ….
What a planning skill may leave a commit to, e.g. a Spec Kit script.
story: &'static strThe heading of the requirement text in a bundle.
constitution: &'static strThe heading of the project-wide rules (Project constitution).
plan: &'static strThe heading of the unit’s plan in the attempt prompt (Feature plan).
plan_short: &'static strThe same in the external agent’s prompt (Plan).
examples: &'static strWhat acceptance tests are derived from.
convergence_task: &'static strA task closing a gap: A task in a Convergence phase.
files: [&'static str; 3]The spec, plan and task list headings, as convergence shows them.
assess: AssessHow convergence is told what to assess.