nrslib · nrslib · Sep 8, 2026 · Sep 5, 2026 · Sep 5, 2026 · Sep 5, 2026
diff --git a/builtins/en/facets/instructions/development-implement-with-reports.md b/builtins/en/facets/instructions/development-implement-with-reports.md
@@ -0,0 +1,3 @@
+{extends:implement}
+
+{{include:instructions/development-input-reports}}
diff --git a/builtins/en/facets/instructions/development-maintenance-with-reports.md b/builtins/en/facets/instructions/development-maintenance-with-reports.md
@@ -0,0 +1,3 @@
+{extends:implement-maintenance}
+
+{{include:instructions/development-input-reports}}
diff --git a/builtins/en/facets/instructions/development-team-with-reports.md b/builtins/en/facets/instructions/development-team-with-reports.md
@@ -0,0 +1,3 @@
+{extends:team-leader-implement}
+
+{{include:instructions/development-input-reports}}
diff --git a/builtins/en/facets/instructions/implement-maintenance.md b/builtins/en/facets/instructions/implement-maintenance.md
@@ -1,5 +1,5 @@
 Implement according to the plan within the causally related scope while preserving existing contracts outside the requested change scope.
-Refer only to files within the Report Directory shown in the Workflow Context. Do not search or reference other report directories.
+Refer to files within the Report Directory shown in the Workflow Context and upstream artifacts explicitly supplied in the input. Do not search or reference other report directories.
 Use reports in the Report Directory as the primary source of truth. If additional context is needed, you may consult Previous Response and conversation history as secondary sources (Previous Response may be unavailable). If information conflicts, prioritize reports in the Report Directory and actual file contents.
 
 {{include:instructions/implement-common}}

diff --git a/builtins/en/facets/instructions/implement.md b/builtins/en/facets/instructions/implement.md
@@ -1,5 +1,5 @@
 Implement according to the plan.
-Refer only to files within the Report Directory shown in the Workflow Context. Do not search or reference other report directories.
+Refer to files within the Report Directory shown in the Workflow Context and upstream artifacts explicitly supplied in the input. Do not search or reference other report directories.
 Use reports in the Report Directory as the primary source of truth. If additional context is needed, you may consult Previous Response and conversation history as secondary sources (Previous Response may be unavailable). If information conflicts, prioritize reports in the Report Directory and actual file contents.
 
 **Test requirements:**

diff --git a/builtins/en/facets/instructions/team-leader-implement.md b/builtins/en/facets/instructions/team-leader-implement.md
@@ -3,7 +3,7 @@
 
 Analyze the implementation task and, if decomposition is appropriate, split into multiple parts for parallel execution.
 
-**Important:** Use the original task and the engine-provided previous response below as the primary sources. The parent Team Leader must not use tools or fill in facts that are not present in them.
+**Important:** Use the original task, upstream artifacts explicitly supplied in the input, and the engine-provided previous response below as the primary sources. The parent Team Leader must not use tools or fill in facts that are not present in them.
 
 {previous_response}
 
@@ -30,6 +30,7 @@ Analyze the implementation task and, if decomposition is appropriate, split into
      - **Reference-only files** (read-only, modification prohibited)
      - **Implementation task** (what and how to implement)
      - **Completion criteria** (implementation of responsible files is complete)
+     - **Upstream obligations and evidence requirements** (include the relevant contents for the assigned scope, preserving existing input IDs and their meaning; do not assume the parent plan is automatically inherited by parts)
    - If tests are already written, instruct parts to implement so existing tests pass
    - Refer to Quality Gates and plan any required verification in a later feedback batch
    - Do not make parallel implementation parts run duplicate full-build or full-test checks

diff --git a/builtins/en/facets/partials/instructions/development-input-reports.md b/builtins/en/facets/partials/instructions/development-input-reports.md
@@ -0,0 +1,13 @@
+## Explicit Upstream Artifacts
+
+Follow the injected plan and use the test report to identify existing tests and unverified areas.
+You may use these supplied artifacts even when they originate from a parent's Report Directory. This does not authorize searching other report directories.
+Do not infer the existence or content of artifacts marked missing. When the input defines IDs, preserve their meaning and associate implementation results and evidence with them. Inputs without IDs do not require new IDs.
+
+### Plan
+
+{report:plan.md}
+
+### Test Report
+
+{report:test-report.md}
diff --git a/builtins/en/workflows/backend-maintenance.yaml b/builtins/en/workflows/backend-maintenance.yaml
@@ -41,7 +41,7 @@ steps:
         - security
         - architecture
         - existing-system
-      implementation_instruction: implement-maintenance
+      implementation_instruction: development-maintenance-with-reports
       review_policy_additions:
         - existing-system-respect
       review_policy:

diff --git a/builtins/en/workflows/cli.yaml b/builtins/en/workflows/cli.yaml
@@ -28,7 +28,7 @@ steps:
       development_knowledge:
         - architecture
         - task-decomposition
-      implementation_instruction: implement
+      implementation_instruction: development-implement-with-reports
       review_policy:
         - coding
         - testing

diff --git a/builtins/en/workflows/development-core.yaml b/builtins/en/workflows/development-core.yaml
@@ -89,7 +89,7 @@ subworkflow:
     implementation_instruction:
       type: facet_ref
       facet_kind: instruction
-      default: implement
+      default: development-implement-with-reports
     scope_report_format:
       type: facet_ref
       facet_kind: report_format

diff --git a/builtins/en/workflows/development-implement-dynamic.yaml b/builtins/en/workflows/development-implement-dynamic.yaml
@@ -28,7 +28,7 @@ subworkflow:
     implementation_instruction:
       type: facet_ref
       facet_kind: instruction
-      default: implement
+      default: development-implement-with-reports
     scope_report_format:
       type: facet_ref
       facet_kind: report_format

diff --git a/builtins/en/workflows/development-implement-team.yaml b/builtins/en/workflows/development-implement-team.yaml
@@ -55,7 +55,7 @@ steps:
         $param: development_policy
       development_knowledge:
         $param: development_knowledge
-      implementation_instruction: team-leader-implement
+      implementation_instruction: development-team-with-reports
       scope_report_format:
         $param: scope_report_format
     team_leader:

diff --git a/builtins/en/workflows/development-implement.yaml b/builtins/en/workflows/development-implement.yaml
@@ -28,7 +28,7 @@ subworkflow:
     implementation_instruction:
       type: facet_ref
       facet_kind: instruction
-      default: implement
+      default: development-implement-with-reports
     scope_report_format:
       type: facet_ref
       facet_kind: report_format

diff --git a/builtins/en/workflows/frontend-maintenance.yaml b/builtins/en/workflows/frontend-maintenance.yaml
@@ -48,7 +48,7 @@ steps:
         - security
         - architecture
         - existing-system
-      implementation_instruction: implement-maintenance
+      implementation_instruction: development-maintenance-with-reports
       reviewer_suite: peer-review-suite-frontend
       review_policy_additions:
         - existing-system-respect

diff --git a/builtins/en/workflows/maintenance.yaml b/builtins/en/workflows/maintenance.yaml
@@ -41,7 +41,7 @@ steps:
         - architecture
         - implementation-semantics
         - existing-system
-      implementation_instruction: implement-maintenance
+      implementation_instruction: development-maintenance-with-reports
       scope_report_format: maintenance-scope
       fix_plan_instruction: scenario-based-fix-plan-from-review-resolution
       fix_plan_report_format: scenario-based-fix-plan

diff --git a/builtins/en/workflows/review-fix-takt-default.yaml b/builtins/en/workflows/review-fix-takt-default.yaml
@@ -50,7 +50,7 @@ steps:
         - architecture
         - task-decomposition
         - implementation-semantics
-      implementation_instruction: implement
+      implementation_instruction: development-implement-with-reports
       review_policy:
         - coding
         - testing

diff --git a/builtins/ja/facets/instructions/development-implement-with-reports.md b/builtins/ja/facets/instructions/development-implement-with-reports.md
@@ -0,0 +1,3 @@
+{extends:implement}
+
+{{include:instructions/development-input-reports}}
diff --git a/builtins/ja/facets/instructions/development-maintenance-with-reports.md b/builtins/ja/facets/instructions/development-maintenance-with-reports.md
@@ -0,0 +1,3 @@
+{extends:implement-maintenance}
+
+{{include:instructions/development-input-reports}}
diff --git a/builtins/ja/facets/instructions/development-team-with-reports.md b/builtins/ja/facets/instructions/development-team-with-reports.md
@@ -0,0 +1,3 @@
+{extends:team-leader-implement}
+
+{{include:instructions/development-input-reports}}
diff --git a/builtins/ja/facets/instructions/implement-maintenance.md b/builtins/ja/facets/instructions/implement-maintenance.md
@@ -1,5 +1,5 @@
 計画に従い、変更対象外の既存契約を保ちつつ、要求と因果関係のある範囲で実装してください。
-Workflow Contextに示されたReport Directory内のファイルのみ参照してください。他のレポートディレクトリは検索/参照しないでください。
+Workflow Contextに示されたReport Directory内のファイルと、入力に明示された上流成果物を参照してください。他のレポートディレクトリは検索/参照しないでください。
 Report Directory内のレポートを一次情報として参照してください。不足情報の補完が必要な場合に限り、Previous Responseや会話履歴を補助的に参照して構いません（Previous Responseは提供されない場合があります）。情報が競合する場合は、Report Directory内のレポートと実際のファイル内容を優先してください。
 
 {{include:instructions/implement-common}}

diff --git a/builtins/ja/facets/instructions/implement.md b/builtins/ja/facets/instructions/implement.md
@@ -1,5 +1,5 @@
 計画に従って実装してください。
-Workflow Contextに示されたReport Directory内のファイルのみ参照してください。他のレポートディレクトリは検索/参照しないでください。
+Workflow Contextに示されたReport Directory内のファイルと、入力に明示された上流成果物を参照してください。他のレポートディレクトリは検索/参照しないでください。
 Report Directory内のレポートを一次情報として参照してください。不足情報の補完が必要な場合に限り、Previous Responseや会話履歴を補助的に参照して構いません（Previous Responseは提供されない場合があります）。情報が競合する場合は、Report Directory内のレポートと実際のファイル内容を優先してください。
 
 **テスト要件:**

diff --git a/builtins/ja/facets/instructions/team-leader-implement.md b/builtins/ja/facets/instructions/team-leader-implement.md
@@ -3,7 +3,7 @@
 
 実装タスクを分析し、分解が適切なら複数パートに分けて並列実行してください。
 
-**重要:** 元のタスクと、以下で engine が渡す前ステップの応答を一次情報として使用してください。親 Team Leader 自身はツールを使わず、これらにない事実を補完しません。
+**重要:** 元のタスク、入力に明示された上流成果物、以下で engine が渡す前ステップの応答を一次情報として使用してください。親 Team Leader 自身はツールを使わず、これらにない事実を補完しません。
 
 {previous_response}
 
@@ -30,6 +30,7 @@
      - **参照専用ファイル**（変更禁止、読み取りのみ可）
      - **実装内容**（何をどのように実装するか）
      - **完了基準**（担当ファイルの実装が完了したこと）
+     - **上流の完了義務と証拠条件**（担当範囲に必要な内容を本文で渡し、入力に既存IDがあればその意味とIDを維持する。partへの親計画の自動継承は前提にしない）
    - テスト済みの場合は「既存テストがパスするよう実装する」と明記する
    - 品質ゲート（Quality Gates）を参照し、必要な検証は後続の feedback batch で計画する
    - 並列の実装パートには、全体ビルド・全体テストを重複して実行させない

diff --git a/builtins/ja/facets/partials/instructions/development-input-reports.md b/builtins/ja/facets/partials/instructions/development-input-reports.md
@@ -0,0 +1,13 @@
+## 明示された上流成果物
+
+以下に注入された計画に従い、テスト報告から作成済みテストと未確認範囲を把握してください。
+これらは親のReport Directory由来でも参照できます。他のレポートディレクトリを自由に検索する許可ではありません。
+欠落と示された成果物の存在や内容を推測しないでください。入力に既存IDがある場合は、その意味を維持して実装結果と証拠を対応付けてください。IDのない入力へ新たなIDを付ける必要はありません。
+
+### 計画
+
+{report:plan.md}
+
+### テスト報告
+
+{report:test-report.md}
diff --git a/builtins/ja/workflows/backend-maintenance.yaml b/builtins/ja/workflows/backend-maintenance.yaml
@@ -41,7 +41,7 @@ steps:
         - security
         - architecture
         - existing-system
-      implementation_instruction: implement-maintenance
+      implementation_instruction: development-maintenance-with-reports
       review_policy_additions:
         - existing-system-respect
       review_policy:

diff --git a/builtins/ja/workflows/cli.yaml b/builtins/ja/workflows/cli.yaml
@@ -28,7 +28,7 @@ steps:
       development_knowledge:
         - architecture
         - task-decomposition
-      implementation_instruction: implement
+      implementation_instruction: development-implement-with-reports
       review_policy:
         - coding
         - testing

diff --git a/builtins/ja/workflows/development-core.yaml b/builtins/ja/workflows/development-core.yaml
@@ -89,7 +89,7 @@ subworkflow:
     implementation_instruction:
       type: facet_ref
       facet_kind: instruction
-      default: implement
+      default: development-implement-with-reports
     scope_report_format:
       type: facet_ref
       facet_kind: report_format

diff --git a/builtins/ja/workflows/development-implement-dynamic.yaml b/builtins/ja/workflows/development-implement-dynamic.yaml
@@ -28,7 +28,7 @@ subworkflow:
     implementation_instruction:
       type: facet_ref
       facet_kind: instruction
-      default: implement
+      default: development-implement-with-reports
     scope_report_format:
       type: facet_ref
       facet_kind: report_format

diff --git a/builtins/ja/workflows/development-implement-team.yaml b/builtins/ja/workflows/development-implement-team.yaml
@@ -55,7 +55,7 @@ steps:
         $param: development_policy
       development_knowledge:
         $param: development_knowledge
-      implementation_instruction: team-leader-implement
+      implementation_instruction: development-team-with-reports
       scope_report_format:
         $param: scope_report_format
     team_leader:

diff --git a/builtins/ja/workflows/development-implement.yaml b/builtins/ja/workflows/development-implement.yaml
@@ -28,7 +28,7 @@ subworkflow:
     implementation_instruction:
       type: facet_ref
       facet_kind: instruction
-      default: implement
+      default: development-implement-with-reports
     scope_report_format:
       type: facet_ref
       facet_kind: report_format

diff --git a/builtins/ja/workflows/frontend-maintenance.yaml b/builtins/ja/workflows/frontend-maintenance.yaml
@@ -48,7 +48,7 @@ steps:
         - security
         - architecture
         - existing-system
-      implementation_instruction: implement-maintenance
+      implementation_instruction: development-maintenance-with-reports
       reviewer_suite: peer-review-suite-frontend
       review_policy_additions:
         - existing-system-respect

diff --git a/builtins/ja/workflows/maintenance.yaml b/builtins/ja/workflows/maintenance.yaml
@@ -41,7 +41,7 @@ steps:
         - architecture
         - implementation-semantics
         - existing-system
-      implementation_instruction: implement-maintenance
+      implementation_instruction: development-maintenance-with-reports
       scope_report_format: maintenance-scope
       fix_plan_instruction: scenario-based-fix-plan-from-review-resolution
       fix_plan_report_format: scenario-based-fix-plan

diff --git a/builtins/ja/workflows/review-fix-takt-default.yaml b/builtins/ja/workflows/review-fix-takt-default.yaml
@@ -50,7 +50,7 @@ steps:
         - architecture
         - task-decomposition
         - implementation-semantics
-      implementation_instruction: implement
+      implementation_instruction: development-implement-with-reports
       review_policy:
         - coding
         - testing
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,3 @@
		{extends:implement}

		{{include:instructions/development-input-reports}}
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,3 @@
		{extends:implement-maintenance}

		{{include:instructions/development-input-reports}}
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,3 @@
		{extends:team-leader-implement}

		{{include:instructions/development-input-reports}}