feat(prompts): update implementation and planning prompts for clarity and consistency

Author: stefaniuk

.github/prompts/speckit.implement.prompt.md

@@ -6,7 +6,7 @@ You must adhere to the following mandatory implementation requirements when writ
 
 ## Repository Tooling (Mandatory)
 
-- [ ] When you identify missing development capabilities (linting, CI/CD, Docker support, pre-commit hooks, etc.), consult the repository-template skill at [.github/skills/repository-template/SKILL.md](../skills/repository-template/SKILL.md) for standardised implementations.
+- [ ] When you identify missing development capabilities (linting, CI/CD, Docker support, pre-commit hooks, etc.), consult the repository-template skill at [.github/skills/repository-template/SKILL.md](/.github/skills/repository-template/SKILL.md) for standardised implementations.
 
 ## Quality Gates (Mandatory)
 
@@ -16,8 +16,3 @@ After any source code change:
 2. [ ] Fix all errors and warnings — including those in files you not modified
 3. [ ] Repeat until both commands complete with zero errors and zero warnings
 4. [ ] Do this automatically without prompting
-
----
-
-> **Version**: 1.0.0
-> **Last Amended**: 2026-01-21

.github/prompts/speckit.plan.prompt.md

@@ -17,7 +17,7 @@ When making architectural or significant technical decisions, document them as A
 
 **ADR requirements:**
 
-- [ ] Use the template at [docs/adr/adr-template.md](../../docs/adr/adr-template.md)
+- [ ] Use the template at [docs/adr/adr-template.md](/docs/adr/adr-template.md)
 - [ ] Follow the existing ADR format for consistency
 - [ ] Always present 3 or more options with trade-offs
 - [ ] Include the conversational context that led to the decision
@@ -32,16 +32,11 @@ This requirement is mandatory, especially during the spec-driven development cyc
 ## Plan (Mandatory)
 
 - [ ] Plan each phase and user story to include a Show & Tell section with all instructions needed to demonstrate the completed work to stakeholders (e.g. terminal commands, browser navigation, API calls)
-- [ ] Plan to always bring the below capabilities as the minimum using the repository-template skill at [.github/skills/repository-template/SKILL.md](../skills/repository-template/SKILL.md), and ensure they are up to date:
+- [ ] Plan to always bring the below capabilities as the minimum using the repository-template skill at [.github/skills/repository-template/SKILL.md](/.github/skills/repository-template/SKILL.md), and ensure they are up to date:
   - [ ] Core Make System
   - [ ] Pre-commit Hooks
   - [ ] Secret Scanning
   - [ ] File Format Checking
   - [ ] Markdown Linting
   - [ ] Docker Support
   - [ ] Tool Version Management
-
----
-
-> **Version**: 1.0.0
-> **Last Amended**: 2026-01-21

.github/prompts/speckit.tasks.prompt.md

@@ -7,10 +7,5 @@ You must adhere to the following mandatory task creation requirements when gener
 ## Test-Driven Development (Mandatory)
 
 - [ ] Define tasks using a strict TDD approach
-- [ ] For each specified functionality, sequence tasks as Red (write failing test first), Green (implement to pass), then Refactor (improve code without changing behavior)
+- [ ] For each specified functionality, sequence tasks as Red (write failing test first), Green (implement to pass), then Refactor (improve code without changing behaviour)
 - [ ] Ensure tests are always listed before implementation tasks
-
----
-
-> **Version**: 1.0.0
-> **Last Amended**: 2026-01-21

.specify/extensions/manifest.yaml

@@ -20,17 +20,14 @@
 #
 #   3. Run: make patch-speckit
 
-# # Default injection points per category
-# defaults:
-#   agents: after-frontmatter
-#   prompts: after-frontmatter
-#   templates: after-frontmatter
+# Default injection points per category
+defaults:
+  agents: after-frontmatter
+  prompts: after-frontmatter
+  templates: after-frontmatter
 
-# # Per-file overrides (filename: injection-strategy)
-# # Examples:
-# #   speckit.specify.agent.md: before-section:## Outline
-# #   tasks-template.md: after-section:## Format
-# overrides:
-#   speckit.implement.agent.md: before-section:## Outline
-#   speckit.specify.prompt.md: after-frontmatter
-#   tasks-template.md: before-section:## Phase 1
+# Per-file overrides (filename: injection-strategy)
+# Examples:
+#   speckit.specify.agent.md: before-section:## Outline
+#   tasks-template.md: after-section:## Format
+overrides: {}

.specify/extensions/prompts/speckit.implement.prompt.ext.md

@@ -0,0 +1,14 @@
+You must adhere to the following mandatory implementation requirements when writing code for features.
+
+## Repository Tooling (Mandatory)
+
+- [ ] When you identify missing development capabilities (linting, CI/CD, Docker support, pre-commit hooks, etc.), consult the repository-template skill at [.github/skills/repository-template/SKILL.md](/.github/skills/repository-template/SKILL.md) for standardised implementations.
+
+## Quality Gates (Mandatory)
+
+After any source code change:
+
+1. [ ] Run `make lint` and `make test`
+2. [ ] Fix all errors and warnings — including those in files you not modified
+3. [ ] Repeat until both commands complete with zero errors and zero warnings
+4. [ ] Do this automatically without prompting

.specify/extensions/prompts/speckit.plan.prompt.ext.md

@@ -0,0 +1,38 @@
+You must adhere to the following mandatory planning requirements when creating a development plan.
+
+## Documentation (Mandatory)
+
+When making architectural or significant technical decisions, document them as Architecture Decision Records (ADRs):
+
+**What requires an ADR:**
+
+- [ ] Architectural style choices (e.g. event-driven vs layered, monolith vs microservices)
+- [ ] Architectural pattern choices (e.g. composition over inheritance, repository pattern, event sourcing)
+- [ ] Language and framework selections
+- [ ] Any other significant technical decision that shapes the system
+
+**ADR requirements:**
+
+- [ ] Use the template at [docs/adr/adr-template.md](/docs/adr/adr-template.md)
+- [ ] Follow the existing ADR format for consistency
+- [ ] Always present 3 or more options with trade-offs
+- [ ] Include the conversational context that led to the decision
+- [ ] Document decisions regardless of whether you made them independently or were guided by the user
+
+This requirement is mandatory, especially during the spec-driven development cycle: `spec` → `plan` → `tasks` → `implement`.
+
+## Toolchain Version (Mandatory)
+
+- [ ] Use the latest stable language, runtime, and framework versions at the time of change, search the internet for the latest versions
+
+## Plan (Mandatory)
+
+- [ ] Plan each phase and user story to include a Show & Tell section with all instructions needed to demonstrate the completed work to stakeholders (e.g. terminal commands, browser navigation, API calls)
+- [ ] Plan to always bring the below capabilities as the minimum using the repository-template skill at [.github/skills/repository-template/SKILL.md](/.github/skills/repository-template/SKILL.md), and ensure they are up to date:
+  - [ ] Core Make System
+  - [ ] Pre-commit Hooks
+  - [ ] Secret Scanning
+  - [ ] File Format Checking
+  - [ ] Markdown Linting
+  - [ ] Docker Support
+  - [ ] Tool Version Management

.specify/extensions/prompts/speckit.tasks.prompt.ext.md

@@ -0,0 +1,7 @@
+You must adhere to the following mandatory task creation requirements when generating development tasks.
+
+## Test-Driven Development (Mandatory)
+
+- [ ] Define tasks using a strict TDD approach
+- [ ] For each specified functionality, sequence tasks as Red (write failing test first), Green (implement to pass), then Refactor (improve code without changing behaviour)
+- [ ] Ensure tests are always listed before implementation tasks