feat: add feature-task schema for lighter child work item gates

Split feature work into two schema tiers: feature-implementation for the
parent container (full spec, holistic review with /simplify) and feature-task
for child work items (task-scope, task-level review). Plugin skills updated
to remain generic — they reference config.yaml for schema discovery rather
than hardcoding specific tag names.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: jpicklyk

.claude/skills/feature-implementation/SKILL.md

@@ -1,11 +1,15 @@
 ---
-description: Guide the full lifecycle of a feature-implementation tagged MCP item — from queue through review
+description: Guide the full lifecycle of a feature-implementation tagged MCP item (the feature container) — from queue through review
 ---
 
 # Feature Implementation Workflow
 
-End-to-end workflow for a `feature-implementation` tagged item. Covers all three phases
-(queue → work → review) with gate-enforced notes at each transition.
+End-to-end workflow for a `feature-implementation` tagged item — the **feature container**
+that holds the specification, plan, and holistic review. Child work items under this
+container use the `feature-task` tag with lighter gates (task-scope instead of full
+specification, task-level review without `/simplify`).
+
+Covers all three phases (queue → work → review) with gate-enforced notes at each transition.
 
 **Usage:** `/feature-implementation [item-uuid]`
 

.claude/skills/implement/SKILL.md

@@ -69,7 +69,7 @@ its own isolated branch automatically. See Worktree Isolation below. Worktree
 branches are also local-only and get squash-merged into `main` after review.
 
 **Branch naming** (for local working branches):
-- `feat/<short-description>` — feature-implementation items
+- `feat/<short-description>` — feature-implementation / feature-task items
 - `fix/<short-description>` — bug-fix items
 - `fix/<grouped-description>` — batch of related bug fixes
 - `chore/<short-description>` — tech debt, refactoring, observations

claude-plugins/task-orchestrator/skills/create-item/SKILL.md

@@ -81,9 +81,9 @@ Read `.taskorchestrator/config.yaml` to discover available note schemas (this is
 
 | Context signal | Schema to apply |
 |----------------|-----------------|
-| Feature, enhancement, new capability | `feature-implementation` (if it exists in config) |
-| Bug, error, crash, unexpected behavior | `bug-fix` (if it exists in config) |
-| Observation, friction, optimization, missing capability | `agent-observation` (if it exists in config) |
+| Feature, enhancement, new capability | Match against feature-related schema keys in config (if any exist) |
+| Bug, error, crash, unexpected behavior | Match against bug-related schema keys in config (if any exist) |
+| Observation, friction, optimization, missing capability | Match against observation-related schema keys in config (if any exist) |
 
 If the inferred schema key exists in the config, apply it as the item's `tags` value. If the key does not exist in the config (e.g., no `bug-fix` schema defined), leave tags empty — do not apply a tag that has no matching schema.
 

claude-plugins/task-orchestrator/skills/manage-schemas/references/example-schemas.md

@@ -35,6 +35,34 @@ feature-implementation:
     guidance: "Note whether a rebuild/deploy was done, what version was bumped to, and whether reconnect was required."
 ```
 
+## `feature-task` (queue + work + review, lighter than feature-implementation)
+
+Schema for child work items under a feature container. Lighter queue gate (task scope instead of full specification) and task-scoped review (no `/simplify` — that happens at the container level).
+
+```yaml
+feature-task:
+  - key: task-scope
+    role: queue
+    required: true
+    description: "What to build — target files, acceptance criteria, constraints."
+    guidance: "Define the narrow scope. Include: what to build, target files, acceptance criteria, constraints. The parent feature spec covers the 'why'."
+  - key: implementation-notes
+    role: work
+    required: true
+    description: "Context handoff — deviations, surprises, decisions affecting dependent work."
+    guidance: "Document decisions not in the task scope. Focus on what downstream agents need."
+  - key: review-checklist
+    role: review
+    required: true
+    description: "Task-level quality gate — scope alignment and test coverage."
+    guidance: "Verify scope alignment, test coverage, no unintended side effects. No /simplify here."
+  - key: session-tracking
+    role: work
+    required: true
+    description: "Session context for retrospective."
+    guidance: "Record outcome, files changed, deviations, friction, test results."
+```
+
 ## `bug-fix` (queue + work, no review)
 
 Lightweight schema for bug fixes — root cause before code, verification after.

claude-plugins/task-orchestrator/skills/post-plan-workflow/SKILL.md

@@ -12,7 +12,7 @@ Plan approval is the green light for the full pipeline. Proceed through all thre
 
 Complete materialization **before** any implementation begins.
 
-1. **Create MCP items** from the approved plan using `create_work_tree` (preferred for structured work with dependencies) or `manage_items` (for individual items). Apply appropriate schema tags (e.g., `tags: "feature-implementation"`) based on the plan — this activates gate enforcement for the item.
+1. **Create MCP items** from the approved plan using `create_work_tree` (preferred for structured work with dependencies) or `manage_items` (for individual items). Apply appropriate schema tags based on the plan and the project's `.taskorchestrator/config.yaml` — this activates gate enforcement for each item. If the config defines separate schemas for containers vs. child tasks, apply the appropriate tag at each level.
 2. **Wire dependency edges** between items — use `BLOCKS` for sequencing, `fan-out`/`fan-in` patterns for parallel work
 3. **Check `expectedNotes` in create responses** — if the item's tags match a schema, the response includes the expected note keys and phases. Fill required queue-phase notes (`requirements`, `acceptance-criteria`, etc.) with content from the plan before advancing.
 4. **Verify all item UUIDs exist** — confirm the full item graph is materialized before proceeding

current/src/test/kotlin/io/github/jpicklyk/mcptask/current/test/TestNoteSchemaService.kt

@@ -27,6 +27,16 @@ class TestNoteSchemaService(
             )
         ))
 
+        /** Feature task schema — lighter gates for child work items under a feature container. */
+        val FEATURE_TASK = TestNoteSchemaService(mapOf(
+            "feature-task" to listOf(
+                NoteSchemaEntry(key = "task-scope", role = "queue", required = true, description = "What to build — target files, acceptance criteria, constraints"),
+                NoteSchemaEntry(key = "implementation-notes", role = "work", required = true, description = "Context handoff — deviations, surprises, decisions"),
+                NoteSchemaEntry(key = "review-checklist", role = "review", required = true, description = "Task-level quality gate — scope alignment and test coverage"),
+                NoteSchemaEntry(key = "session-tracking", role = "work", required = true, description = "Session context for retrospective")
+            )
+        ))
+
         /** Bug fix schema — queue and work only, no review phase. */
         val BUG_FIX = TestNoteSchemaService(mapOf(
             "bug-fix" to listOf(