You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Put in thirdshift configuration the prompt and skills so that users can tweak the format of those. #118
Factory skills are embedded in the binary, Session prompts are generated internally, and User config currently has no persistent override mechanism. A repository's own instructions are a separate input.
Next decisions: should an override replace a complete prompt/skill or append user instructions; which Session purposes and skills are covered; and how should overrides survive a binary or upstream-skill upgrade? Keep embedded defaults usable without external files (ADR 0001), define behavior for missing/invalid overrides, and make the effective instructions inspectable. Coordinate with #660's per-Command text and #321's upstream synchronization; neither covers this persistent configuration request.
Related: #877 (Spec: Custom processes) lists overriding a built-in's prompts as out of scope and leaves that to this issue. Once the Ticket run becomes a Built-in process (a later Spec, per #877's Q1.5 in docs/grill-with-docs/877-composable-by-file.md), overriding its prompts may be easier to build as a copied and renamed Custom process, or as Archon-style additions to the default prompt (docs/research/file-defined-factories.md).
Activity
JacobStephens2 commentedon Oct 17, 2026
Triage Notes
Factory skills are embedded in the binary, Session prompts are generated internally, and User config currently has no persistent override mechanism. A repository's own instructions are a separate input.
Next decisions: should an override replace a complete prompt/skill or append user instructions; which Session purposes and skills are covered; and how should overrides survive a binary or upstream-skill upgrade? Keep embedded defaults usable without external files (ADR 0001), define behavior for missing/invalid overrides, and make the effective instructions inspectable. Coordinate with #660's per-Command text and #321's upstream synchronization; neither covers this persistent configuration request.
JacobStephens2 commentedon Oct 26, 2026
Related: #877 (Spec: Custom processes) lists overriding a built-in's prompts as out of scope and leaves that to this issue. Once the Ticket run becomes a Built-in process (a later Spec, per #877's Q1.5 in
docs/grill-with-docs/877-composable-by-file.md), overriding its prompts may be easier to build as a copied and renamed Custom process, or as Archon-style additions to the default prompt (docs/research/file-defined-factories.md).