💫 Toolkit to help you get started with SDD or any other process!
Update prompts
Den Delimarsky 🌺895bcbef0015
diff --git a/templates/commands/constitution.md b/templates/commands/constitution.mdindex 583ff24cb..671d2c9ab 100644--- a/templates/commands/constitution.md+++ b/templates/commands/constitution.md@@ -2,6 +2,12 @@description: Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.---+The user input to you can be provided directly by the agent or in `$ARGUMENTS` - you **MUST** consider it before proceeding with the prompt (if not empty).++User input:++$ARGUMENTS+You are updating the project constitution at `/memory/constitution.md`. This file is a TEMPLATE containing placeholder tokens in square brackets (e.g. `[PROJECT_NAME]`, `[PRINCIPLE_1_NAME]`). Your job is to (a) collect/derive concrete values, (b) fill the template precisely, and (c) propagate any amendments across dependent artifacts.Follow this execution flow:diff --git a/templates/commands/implement.md b/templates/commands/implement.mdindex e017d8ea6..19e45f7fe 100644--- a/templates/commands/implement.md+++ b/templates/commands/implement.md@@ -5,7 +5,11 @@ scripts:ps: scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks----Given the current feature context, do this:+The user input to you can be provided directly by the agent or in `$ARGUMENTS` - you **MUST** consider it before proceeding with the prompt (if not empty).++User input:++$ARGUMENTS1. Run `{SCRIPT}` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute.diff --git a/templates/commands/plan.md b/templates/commands/plan.mdindex 18a0b5c64..afb9c900b 100644--- a/templates/commands/plan.md+++ b/templates/commands/plan.md@@ -5,6 +5,12 @@ scripts:ps: scripts/powershell/setup-plan.ps1 -Json---+The user input to you can be provided directly by the agent or in `$ARGUMENTS` - you **MUST** consider it before proceeding with the prompt (if not empty).++User input:++$ARGUMENTS+Given the implementation details provided as an argument, do this:1. Run `{SCRIPT}` from the repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, BRANCH. All future file paths must be absolute.diff --git a/templates/commands/specify.md b/templates/commands/specify.mdindex 9a6a3b361..474f7b026 100644--- a/templates/commands/specify.md+++ b/templates/commands/specify.md@@ -5,6 +5,12 @@ scripts:ps: scripts/powershell/create-new-feature.ps1 -Json "{ARGS}"---+The user input to you can be provided directly by the agent or in `$ARGUMENTS` - you **MUST** consider it before proceeding with the prompt (if not empty).++User input:++$ARGUMENTS+The text the user typed after `/specify` in the triggering message **is** the feature description. Assume you always have it available in this conversation even if `{ARGS}` appears literally below. Do not ask the user to repeat it unless they provided an empty command.Given that feature description, do this:diff --git a/templates/commands/tasks.md b/templates/commands/tasks.mdindex 3e2b226e5..792dd2393 100644--- a/templates/commands/tasks.md+++ b/templates/commands/tasks.md@@ -5,7 +5,11 @@ scripts:ps: scripts/powershell/check-prerequisites.ps1 -Json----Given the context provided as an argument, do this:+The user input to you can be provided directly by the agent or in `$ARGUMENTS` - you **MUST** consider it before proceeding with the prompt (if not empty).++User input:++$ARGUMENTS1. Run `{SCRIPT}` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute.2. Load and analyze available design documents: