shinpr · shinpr · May 3, 2026 · May 3, 2026 · May 3, 2026 · May 3, 2026
diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json
@@ -12,7 +12,7 @@
       "name": "dev-workflows",
       "source": "./dev-workflows",
       "strict": true,
-      "version": "0.17.1",
+      "version": "0.18.0",
       "description": "Skills + Subagents for backend development - Use skills for coding guidance, or run recipe workflows for full orchestrated agentic coding with specialized agents",
       "author": {
         "name": "Shinsuke Kagawa",
@@ -58,6 +58,7 @@
         "./skills/ai-development-guide",
         "./skills/coding-principles",
         "./skills/documentation-criteria",
+        "./skills/external-resource-context",
         "./skills/implementation-approach",
         "./skills/integration-e2e-testing",
         "./skills/recipe-add-integration-tests",
@@ -82,7 +83,7 @@
       "name": "dev-workflows-frontend",
       "source": "./dev-workflows-frontend",
       "strict": true,
-      "version": "0.17.1",
+      "version": "0.18.0",
       "description": "Skills + Subagents for React/TypeScript - Use skills for coding guidance, or run recipe workflows for full orchestrated agentic coding with specialized agents",
       "author": {
         "name": "Shinsuke Kagawa",
@@ -121,6 +122,7 @@
         "./agents/task-decomposer.md",
         "./agents/task-executor-frontend.md",
         "./agents/technical-designer-frontend.md",
+        "./agents/ui-analyzer.md",
         "./agents/ui-spec-designer.md",
         "./agents/verifier.md",
         "./agents/work-planner.md"
@@ -129,10 +131,12 @@
         "./skills/ai-development-guide",
         "./skills/coding-principles",
         "./skills/documentation-criteria",
+        "./skills/external-resource-context",
         "./skills/frontend-ai-guide",
         "./skills/implementation-approach",
         "./skills/integration-e2e-testing",
         "./skills/recipe-diagnose",
+        "./skills/recipe-front-adjust",
         "./skills/recipe-front-build",
         "./skills/recipe-front-design",
         "./skills/recipe-front-plan",
@@ -150,7 +154,7 @@
       "name": "dev-skills",
       "source": "./dev-skills",
       "strict": true,
-      "version": "0.17.1",
+      "version": "0.18.0",
       "description": "Lightweight skills for users with existing workflows - coding best practices, testing principles, and design guidelines without recipe workflows or agents",
       "author": {
         "name": "Shinsuke Kagawa",
@@ -173,6 +177,7 @@
         "./skills/ai-development-guide",
         "./skills/coding-principles",
         "./skills/documentation-criteria",
+        "./skills/external-resource-context",
         "./skills/frontend-ai-guide",
         "./skills/implementation-approach",
         "./skills/integration-e2e-testing",

diff --git a/README.md b/README.md
diff --git a/agents/quality-fixer-frontend.md b/agents/quality-fixer-frontend.md
@@ -2,7 +2,7 @@
 name: quality-fixer-frontend
 description: Specialized agent for fixing quality issues in frontend React projects. Executes all verification and fixing tasks including React Testing Library tests in a completely self-contained manner. Takes responsibility for fixing all quality errors until all checks pass. MUST BE USED PROACTIVELY when any quality-related keywords appear (quality/check/verify/test/build/lint/format/type/fix) or after code changes. Handles all verification and fixing tasks autonomously.
 tools: Bash, Read, Edit, MultiEdit, TaskCreate, TaskUpdate
-skills: typescript-rules, test-implement, frontend-ai-guide
+skills: typescript-rules, test-implement, frontend-ai-guide, external-resource-context
 ---
 
 You are an AI assistant specialized in quality assurance for frontend React projects.
@@ -72,6 +72,8 @@ Apply the indicators below to files within scope only. Files outside the scope g
 - Add verified mechanisms to the quality check command list
 - If a listed mechanism cannot be found or executed, note it in the output and continue to the next mechanism
 
+**External Resources Consultation**: When a quality check references a resource recorded in `docs/project-context/external-resources.md` or in a UI Spec / Design Doc / Work Plan "External Resources Used" entry, consult it per the external-resource-context skill (Reference Protocol). When the resource is referenced but unreachable, escalate via `blocked` with `reason: "Execution prerequisites not met"` and populate `missingPrerequisites`.
+
 ### Step 3: Execute Quality Checks
 Follow frontend-ai-guide skill "Quality Check Workflow" section:
 - Basic checks (lint, format, build)

diff --git a/agents/quality-fixer.md b/agents/quality-fixer.md
@@ -2,7 +2,7 @@
 name: quality-fixer
 description: Specialized agent for fixing quality issues in software projects. Executes all verification and fixing tasks related to code quality, correctness guarantees, testing, and building in a completely self-contained manner. Takes responsibility for fixing all quality errors until all tests pass. MUST BE USED PROACTIVELY when any quality-related keywords appear (quality/check/verify/test/build/lint/format/correctness/fix) or after code changes. Handles all verification and fixing tasks autonomously.
 tools: Bash, Read, Edit, MultiEdit, TaskCreate, TaskUpdate
-skills: coding-principles, testing-principles, ai-development-guide
+skills: coding-principles, testing-principles, ai-development-guide, external-resource-context
 ---
 
 You are an AI assistant specialized in quality assurance for software projects.
@@ -69,6 +69,8 @@ Apply the indicators below to files within scope only. Files outside the scope g
 - Add verified mechanisms to the quality check command list
 - If a listed mechanism cannot be found or executed, note it in the output and continue to the next mechanism
 
+**External Resources Consultation**: When a quality check references a resource recorded in `docs/project-context/external-resources.md` or in a Design Doc / Work Plan "External Resources Used" entry, consult it per the external-resource-context skill (Reference Protocol). When the resource is referenced but unreachable, escalate via `blocked` with `reason: "Execution prerequisites not met"` and populate `missingPrerequisites`.
+
 ### Step 3: Execute Quality Checks
 Follow ai-development-guide skill "Quality Check Workflow" section:
 - Basic checks (lint, format, build)

diff --git a/agents/task-executor-frontend.md b/agents/task-executor-frontend.md
@@ -2,7 +2,7 @@
 name: task-executor-frontend
 description: Executes React implementation completely self-contained following frontend task files. Use when frontend task files exist, or when "frontend implementation/React implementation/component creation" is mentioned. Asks no questions, executes consistently from investigation to implementation.
 tools: Read, Edit, Write, MultiEdit, Bash, Grep, Glob, LS, TaskCreate, TaskUpdate
-skills: typescript-rules, test-implement, frontend-ai-guide, implementation-approach
+skills: typescript-rules, test-implement, frontend-ai-guide, implementation-approach, external-resource-context
 ---
 
 You are a specialized AI assistant for reliably executing frontend implementation tasks.
@@ -154,6 +154,9 @@ Fallback (only when no path is passed): glob `docs/plans/tasks/*-task-*.md` and
    - API Specifications → Understand endpoints, parameters, response formats (for MSW mocking)
    - Overall Design Document → Understand system-wide context
 
+#### External Resources Consultation (When Relevant)
+When the task file's "Investigation Targets", "Dependencies", or any referenced Design Doc / UI Spec / Work Plan entry points to a resource recorded in `docs/project-context/external-resources.md` or to a row in an "External Resources Used" table, consult it per the external-resource-context skill (Reference Protocol). Escalate with `reason: "external_resource_unspecified"` when a needed resource is not found.
+
 #### Step 2 Completion Gate [BLOCKING when the Investigation Targets section contains one or more concrete file paths]
 
 This gate runs only when the task file's "Investigation Targets" section lists at least one concrete file path (placeholder-only or empty sections do not trigger the gate).

diff --git a/agents/task-executor.md b/agents/task-executor.md
@@ -2,7 +2,7 @@
 name: task-executor
 description: Executes implementation completely self-contained following task files. Use when task files exist in docs/plans/tasks/, or when "execute task/implement task/start implementation" is mentioned. Asks no questions, executes consistently from investigation to implementation.
 tools: Read, Edit, Write, MultiEdit, Bash, Grep, Glob, LS, TaskCreate, TaskUpdate
-skills: coding-principles, testing-principles, ai-development-guide, implementation-approach
+skills: coding-principles, testing-principles, ai-development-guide, implementation-approach, external-resource-context
 ---
 
 You are a specialized AI assistant for reliably executing individual tasks.
@@ -152,6 +152,9 @@ Fallback (only when no path is passed): glob `docs/plans/tasks/*-task-*.md` and
    - Data Schema → Understand table structure, relationships
    - Overall Design Document → Understand system-wide context
 
+#### External Resources Consultation (When Relevant)
+When the task file's "Investigation Targets", "Dependencies", or any referenced Design Doc / Work Plan entry points to a resource recorded in `docs/project-context/external-resources.md` or to a row in an "External Resources Used" table, consult it per the external-resource-context skill (Reference Protocol). Escalate with `reason: "external_resource_unspecified"` when a needed resource is not found.
+
 #### Step 2 Completion Gate [BLOCKING when the Investigation Targets section contains one or more concrete file paths]
 
 This gate runs only when the task file's "Investigation Targets" section lists at least one concrete file path (placeholder-only or empty sections do not trigger the gate).