القائمة
SDD Phases 3-4 for provider development. TDD implementation and validation from an existing provider-design-{resource}.md.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
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.
استنادا إلى تصنيف SOC المهني
| name | tf-provider-implement |
| description | SDD Phases 3-4 for provider development. TDD implementation and validation from an existing provider-design-{resource}.md. |
| source | image |
Builds and validates a Terraform provider resource from specs/{FEATURE}/provider-design-{resource}.md using TDD.
Post progress: bash .foundations/scripts/bash/post-issue-progress.sh $ISSUE_NUMBER "<step>" "<status>" "<summary>"
Checkpoint: bash .foundations/scripts/bash/checkpoint-commit.sh --dir . --prefix feat "<step_name>"
$FEATURE and $RESOURCE from $ARGUMENTS or current git branch name.specs/{FEATURE}/provider-design-{resource}.md exists via Glob. Stop if missing — tell user to run /tf-provider-plan first. Capture $DESIGN_FILE.$ISSUE_NUMBER from $ARGUMENTS or gh issue list --search "$FEATURE".tf-provider-test-writer agents with $DESIGN_FILE. Verify _test.go exists. Checkpoint.- [ ] lines).tf-provider-developer agent → go build + go test -c → checkpoint.go vet ./.... Fix until clean. Verify all §6 items marked [x].tf-provider-validator agents with $DESIGN_FILE and service directory. If auto-fixes applied, run go build to confirm.tf-provider-developer targeted at specific issues. Repeat until resolved.specs/{FEATURE}/reports/ using the tf-report-template skill provider template.$ISSUE_NUMBER.Report: build pass/fail, test compilation, acceptance test results (if run), validation status, PR link.