メニュー
Resolves and records one external evidence source required by a current design or verification decision. Use when repository and supplied evidence cannot determine that decision.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/shinpr/codex-workflows --skill external-resource-contextコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Proposes and, after user confirmation, creates or maintains docs/project-context/quality.yaml from repository-specific review requirements. Use when asked to generate or update a repository quality profile.
Execute an approved backend Work Plan autonomously through task execution, quality fixes, commits, and final verification.
Execute an approved frontend Work Plan autonomously through frontend implementation, quality fixes, commits, and final verification.
SOC 職業分類に基づく
SKILL.md を表示中
| name | external-resource-context |
| description | Resolves and records one external evidence source required by a current design or verification decision. Use when repository and supplied evidence cannot determine that decision. |
This skill resolves a concrete external evidence dependency for a current design or verification decision, records its stable access method, and lets later consumers reuse that evidence.
Potential resources include design origin, design system, API or database schema sources, IaC, and verification environments. A workflow selects only the resource axis needed by its current decision.
In scope: resolving a named external evidence need, storage location, single-source ownership, and lookup of a known resource.
Freshness handling: record access methods and feature identifiers here. The consuming workflow checks current resource content at use time.
| Tier | Location | Holds | Update Frequency |
|---|---|---|---|
| Project | docs/project-context/external-resources.md | Environment-stable facts: resource labels, presence, and access methods | When the project environment changes |
| Feature | ## External Resources Used section in the relevant UI Spec or Design Doc | Feature-specific identifiers that reference project-tier labels | Per feature |
The project tier owns environment facts such as URLs, MCP server names, file paths, commands, and secret-store locations. Feature-tier sections list feature-specific identifiers such as design node ids, API paths, schema names, or IaC module names, then reference the project-tier label.
| Condition | Action |
|---|---|
| Repository or supplied evidence resolves the current decision | Continue without hearing |
| A recorded matching axis has a usable access method | Reuse it without hearing |
| A named axis required by the current decision is missing or stale | Ask only for that axis and the access method needed to inspect it |
State which decision or verification result the requested resource controls. Leave unrelated axes unrecorded. Use N/A only for a selected or inspected axis confirmed to be outside the project.
Load the domain reference matching the current task:
| Task type | References to load |
|---|---|
| Frontend UI work | references/frontend.md |
| Backend or data work | references/backend.md |
| API contract work | references/api.md |
| Infrastructure or deployment | references/infra.md |
| Fullstack | Load each relevant domain reference |
Each domain reference defines candidate axes and question templates. Record only the axes selected for the current decision; use N/A when an inspected axis is outside the current project.
Ask for the selected axis, its stable access method, and the feature identifier when known. Accept MCP server name, URL, file path, command, repository-owned source, or existing implementation. One answer completes the hearing when it makes the named decision inspectable.
When the resource remains unavailable, return the exact decision it leaves unsupported. The consuming workflow first selects a repository-evidenced alternative, contract substitute, or explicit fallback that preserves the approved outcome. Continue without external-owner approval; request user input when no available option can resolve a product requirement or approved major design decision.
After hearing completes:
docs/project-context/external-resources.md, creating docs/project-context/ as needed.External Resources Used section with project-tier labels plus feature-specific identifiers.Consumers resolve external context in this order:
docs/project-context/external-resources.md.Codex custom agents inherit parent mcp_servers when the agent file omits mcp_servers. Preserve that inheritance for agents that may need project-specific MCP tools. Reserve MCP enabled_tools for a deliberately narrow server-level allow list.
The project-tier file follows references/template.md. Feature-tier sections use the fixed heading External Resources Used; heading level follows the parent document structure.