nitm-ai-dev-toolkit 5.1.3 → 5.2.1

package/src/repo/.github/prompts/constitution.prompt.md

@@ -1,6 +1,6 @@
 ---
 description: Create or update the project constitution
-tools: ["read", "search", "edit"]
+tools: ["read", "search", "edit", "agent"]
 argument-hint: "no arguments required"
 ---
 

package/src/repo/.github/prompts/create-skill.prompt.md

@@ -1,6 +1,6 @@
 ---
 description: Create a new agent skill following VS Code and agentskills.io specifications
-tools: ["read", "search", "edit"]
+tools: ["read", "search", "edit", "agent"]
 tags: [skill-creation, agent-skills, documentation, automation]
 version: 1.0.0
 argument-hint: "skill purpose or description"

package/src/repo/.github/prompts/implement-feature.prompt.md

@@ -1,6 +1,6 @@
 ---
 description: Implement a feature by completing tasks sequentially
-tools: ["read", "search", "edit", "terminal"]
+tools: ["read", "search", "edit", "terminal", "agent"]
 argument-hint: "issue key or task file path"
 ---
 
@@ -11,6 +11,6 @@ argument-hint: "issue key or task file path"
 | Agent | When to use |
 |-------|-------------|
 | `fixer` | Bounded feature work — spec is clear, files are known |
-| `feature-builder` | Complex feature — needs research, planning, and coordination |
+| `feature-builder` | Complex feature build — builder only; the orchestrator still runs the review |
 
 **CRITICAL: READ:** [.claude/prompt-snippets/implement-feature.md](../../.claude/prompt-snippets/implement-feature.md).

package/src/repo/.github/prompts/implement-fixes.prompt.md

@@ -1,6 +1,6 @@
 ---
 description: Implement bug fixes with proper tracking and validation
-tools: ["read", "search", "edit", "terminal"]
+tools: ["read", "search", "edit", "terminal", "agent"]
 argument-hint: "issue key or fix description"
 ---
 

package/src/repo/.github/prompts/implement.prompt.md

@@ -1,6 +1,6 @@
 ---
 description: Implement features based on a task list or specification
-tools: ["read", "search", "edit", "runInTerminal", "terminalLastCommand"]
+tools: ["read", "search", "edit", "runInTerminal", "terminalLastCommand", "agent"]
 argument-hint: "task list or specification"
 ---
 

package/src/repo/.github/prompts/plan.prompt.md

@@ -1,6 +1,6 @@
 ---
 description: Create an implementation plan for a feature
-tools: ["read", "search"]
+tools: ["read", "search", "edit", "agent"]
 argument-hint: "issue key or spec file path"
 ---
 

package/src/repo/.opencode/commands/bootstrap-patch.md

@@ -9,7 +9,7 @@ description: "Patch AI instructions by fetching updates from the toolkit repo an
 | Agent | When to use |
 |-------|-------------|
 | `fixer` | Standard patch — incremental changes to existing config |
-| `planner` | Complex patch — cross-cutting changes needing analysis first |
+| `reviewer` | Independent read-only review before approval and after apply |
 
 ## Arguments
 

package/src/repo/.opencode/commands/implement-feature.md

@@ -9,7 +9,7 @@ description: "Implement a feature by completing tasks sequentially"
 | Agent | When to use |
 |-------|-------------|
 | `fixer` | Bounded feature work — spec is clear, files are known |
-| `feature-builder` | Complex feature — needs research, planning, and coordination |
+| `feature-builder` | Complex feature build — builder only; the orchestrator still runs the review |
 
 ## Arguments
 

package/src/repo/AGENTS.md

@@ -395,10 +395,14 @@ Documentation updates are **mandatory before committing** any feature or fix. Se
 - Reference `docs/constitution.md` for project principles and governance
 - Include all doc changes in the same commit/PR as the code
 
+**Supplied-task exception (`implement`, `implement-feature`, `implement-fixes` only):** the task supplied to these commands replaces the spec and plan prerequisites. Do not create or require `spec.md` or `plan.md` for the feature or fix unless the user asks for them. Every other applicable item in the [documentation checklist](.claude/rules-snippets/documentation.md) still applies, including the fix log, `CHANGELOG.md`, `docs/api/`, and `README.md`.
+
+**Requirement-only planning exception:** For `/plan` without an existing specification, preserve the original supplied requirements and acceptance criteria in `plan.md` under **Requirements Source** and **Acceptance Criteria**; do not require or create `spec.md`. `/tasks` and `/assign-tasks` consume that plan source when no specification exists; keep acceptance criteria out of the slim task checklist. This exception overrides the spec prerequisite and mandatory spec-first sequence above and in the documentation checklist only for these planning artifacts. It does not authorize implementation, replace artifact review, waive required human approvals, or change any other documentation duties. The separate implementation-command supplied-task exception remains unchanged.
+
 ## Contributing
 
 **Standards:** Follow {{FRAMEWORK}} and {{LANGUAGE}} best practices
-**Process:** Feature branch → spec/plan docs → tests → implementation → update docs → lint → build → PR
+**Process:** Feature branch → spec/plan docs (subject to the requirement-only planning and supplied-task exceptions above) → tests → implementation → update docs → lint → build → PR
 
 ## Related Documentation