Design prompt and seed-text config sources with lightweight templating #1343

New issue

Open

opened 2026-07-15 07:09:09 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-15 07:09:09 +00:00

Member

Parent

ward#1273

Problem

Ward has director doctrine spread across AGENTS.md text, seed prompts, help/docs, and other launch-time prose. Kai needs a clearer boundary for what belongs where before ward#1273 can be safely implemented.

What to decide

Design the ownership split for role/agent guidance text and move toward config-owned prompt/seed sources with lightweight interpolation.

Scope

Inventory the current places that feed director/engineer behavior text: AGENTS.md, seed prompts, role prompts, generated issue context, command help, and docs.
Define what belongs in repo-authored AGENTS.md versus ward-owned seed prompts versus generated launch context.
Propose a config directory layout for ward-owned prompt/seed fragments.
Define a small interpolation surface for known variables such as role, workflow, repo ref, issue ref, harness, model, and read-only/local-push state.
Keep templating intentionally lightweight. Do not build a general prompt framework.
Name the implementation steps needed before ward#1273 can become headless again.

Non-goals

Do not rewrite every prompt in this issue.
Do not add a broad template language.
Do not change merge policy here.

Decision context

Kai flagged ward#1273 as premature because she needs a handle on what goes into AGENTS.md versus seed prompt versus other launch prose. The prerequisite is reasonable if bounded to config-owned prompt sources and light variable interpolation.

## Parent ward#1273 ## Problem Ward has director doctrine spread across AGENTS.md text, seed prompts, help/docs, and other launch-time prose. Kai needs a clearer boundary for what belongs where before ward#1273 can be safely implemented. ## What to decide Design the ownership split for role/agent guidance text and move toward config-owned prompt/seed sources with lightweight interpolation. ## Scope - Inventory the current places that feed director/engineer behavior text: AGENTS.md, seed prompts, role prompts, generated issue context, command help, and docs. - Define what belongs in repo-authored AGENTS.md versus ward-owned seed prompts versus generated launch context. - Propose a config directory layout for ward-owned prompt/seed fragments. - Define a small interpolation surface for known variables such as role, workflow, repo ref, issue ref, harness, model, and read-only/local-push state. - Keep templating intentionally lightweight. Do not build a general prompt framework. - Name the implementation steps needed before ward#1273 can become headless again. ## Non-goals - Do not rewrite every prompt in this issue. - Do not add a broad template language. - Do not change merge policy here. ## Decision context Kai flagged ward#1273 as premature because she needs a handle on what goes into AGENTS.md versus seed prompt versus other launch prose. The prerequisite is reasonable if bounded to config-owned prompt sources and light variable interpolation.

coilyco-ops added the

consult

labels

2026-07-15 07:09:09 +00:00