メニュー
SDD Phases 1-2 for provider development. Clarify requirements, research, produce provider-design-{resource}.md, and await human approval before any code is written.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Internal helper contract for calling the codex-companion runtime from Claude Code
Comprehensive guide for Terraform code style, formatting, and best practices based on HashiCorp's official standards and Azure Verified Modules (AVM) requirements. Use when writing or reviewing Terraform configurations, formatting code, organizing files and modules, establishing team conventions, managing version control, ensuring code quality and consistency across infrastructure projects, or developing Azure Verified Modules.
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Design engineering for Codex. Build interfaces with craft, memory, and enforcement. Maintains consistent design decisions across sessions - make choices once, enforce them automatically.
Implement plan using concurrent opus agents and verify completion
Deterministic integration test coverage analysis using off-the-shelf tooling. Use this skill whenever the user asks about test coverage, coverage gaps, untested code, what needs testing, or wants to improve integration test coverage. Also trigger when the user says 'run coverage', 'check coverage', 'coverage report', 'what's untested', 'find gaps', or has just implemented a feature and wants to know what integration tests are missing. This skill runs real tools and produces data-driven reports — not guesswork.
| name | tf-provider-plan |
| description | SDD Phases 1-2 for provider development. Clarify requirements, research, produce provider-design-{resource}.md, and await human approval before any code is written. |
| source | image |
Produces specs/{FEATURE}/provider-design-{resource}.md from requirements. Stops for human approval before any code is written.
Post progress at key steps: bash .foundations/scripts/bash/post-issue-progress.sh $ISSUE_NUMBER "<step>" "<status>" "<summary>". Valid status values: started, in-progress, complete, failed.
Checkpoint after each phase: bash .foundations/scripts/bash/checkpoint-commit.sh "<step_name>". The <step_name> must be a short hyphenated identifier (e.g., "clarify", "research-and-design", "design-approved") — NOT a sentence or file path.
bash .foundations/scripts/bash/validate-env.sh --json. Stop if gate_passed=false. Then separately verify Go is available: go version (Go >= 1.21 required). Stop if Go is not installed or version is insufficient..foundations/templates/issue-body-template.md, fill in the placeholders with parsed requirements, and run gh issue create --title "Provider Resource: {provider}_{service}_{resource}" --body "$FILLED_BODY". Capture $ISSUE_NUMBER. Update the issue body again after Step 6 (clarification) to include API decisions and scope boundaries.bash .foundations/scripts/bash/create-new-feature.sh --json --workflow provider --issue $ISSUE_NUMBER --short-name "<resource-name>" "<feature description>". Parse the JSON output to capture $BRANCH_NAME as $FEATURE.tf-domain-category skill — focus on API behavior ambiguity, state management decisions (ForceNew vs in-place update), and error handling patterns.AskUserQuestion. Must include update-behavior (ForceNew vs in-place), test environment, and security questions.tf-provider-research subagents for API/SDK docs, Plugin Framework patterns, existing provider implementations, and import/state patterns. Wait for all to complete. Verify research files exist at specs/{FEATURE}/research-*.md via Glob.tf-provider-design agent with FEATURE path, RESOURCE name, and clarified requirements. The agent reads the constitution, design template, and research files from specs/{FEATURE}/research-*.md itself. Output: specs/{FEATURE}/provider-design-{resource}.md.specs/{FEATURE}/provider-design-{resource}.md exists via Glob. Re-launch once if missing.## 1. Purpose through ## 7. Open Questions). Fix inline if any missing.AskUserQuestion: attribute counts, CRUD operations, test scenario counts, checklist items. Options: approve, review file first, request changes.Design approved at specs/{FEATURE}/provider-design-{resource}.md. Run /tf-provider-implement $FEATURE $RESOURCE to build.