refine(task-executor): add Unimplemented Dependency Handling rule - #182
Merged
shinpr merged 3 commits intoJun 29, 2026
Merged
Conversation
Define how the executor handles a dependency that is absent or unimplemented. A missing dependency is a stop condition only when preserving the required contract needs it and no local, reversible construct can stand in: - Establish the required contract from an already-read source first; when the contract source itself is missing (a `Dependencies:` deliverable that does not exist and no read source defines it), escalate via design_compliance_violation — a stand-in cannot preserve an undefined contract. - One or more interchangeable local constructs preserve the contract → proceed and record the integration handoff in Investigation Notes. - No construct preserves the contract, or constructs differ on an architectural trade-off → escalate via design_compliance_violation (reusing the existing escalation type, no new enum). Applied to both agents-en/task-executor.md and agents-en/task-executor-frontend.md (frontend adapts terminology: UI Spec, component hierarchy / data flow direction). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ja sources Port the Unimplemented Dependency Handling rule to the Japanese source agents, matching the files' established tone and terminology (代替 for stand-in, 垂直スライス for vertical slice, Step4 中核メカニズム 保全チェック, 鉄則; Design Doc / UI Spec / Target Files / Investigation Notes kept in English per file convention). - Unify "preserve" as 保全 throughout (契約保全 stub/adapter), consistent with Step4 中核メカニズム保全チェック. - Keep "exact undecided decision" precision as 具体的な未決の判断. Keeps both ja agents in sync with the en sources committed in 7fd38a5. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add Unimplemented Dependency Handling rule to task-executor / -frontend (en/ja). See CHANGELOG for details. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an explicit Unimplemented Dependency Handling rule to the
task-executorandtask-executor-frontendagents (en + ja sources), plus a patch release.When Pre-implementation Verification finds a dependency the task requires is absent or unimplemented, the executor previously had no defined branch — it could either over-eagerly block or invent a substitute. This rule makes the decision explicit and machine-checkable:
Dependencies:deliverable read at Step 2). When the dependency is aDependencies:deliverable that does not exist and no read source defines the contract, the contract is undeterminable → escalate asdesign_compliance_violation(a stand-in cannot preserve an undefined contract).design_compliance_violation, populating every required field (details.design_doc_expectation,details.actual_situation,details.why_cannot_implement,details.attempted_approaches[],claude_recommendation).Reuses the existing
design_compliance_violationescalation type — no new enum value. Consistent with the existing Iron Rule and Step 4 Core Mechanism Preservation Check.Changes
7fd38a5— en sources (agents-en/task-executor.md,agents-en/task-executor-frontend.md)d0c1da5— ja sources mirrored, matching the files' established tone and terminology (代替,垂直スライス,Step4 中核メカニズム保全チェック,鉄則; Design Doc / UI Spec / Target Files / Investigation Notes kept in English per file convention; "preserve" unified as保全)6c2e918— release 1.25.1 (package.json,CHANGELOG.md)Scope notes
Edits are in the canonical
agents-en/andagents-ja/sources; the active.claude/agents/is sync-generated byscripts/set-language.js.check:skills-indexpasses (28 skills consistent across en/ja).🤖 Generated with Claude Code