메뉴
SDD Phases 1-2. Clarify requirements, research, produce design.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-module-plan |
| description | SDD Phases 1-2. Clarify requirements, research, produce design.md, and await human approval before any code is written. |
| source | image |
| executionSkill | tf-module-implement |
Produces specs/{FEATURE}/design.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.$ARGUMENTS for module name, provider, and description. Ask via AskUserQuestion if incomplete..foundations/templates/issue-body-template.md, fill in the placeholders with parsed requirements, and run gh issue create --title "Module: {name}" --body "$FILLED_BODY". Capture $ISSUE_NUMBER. Update the issue body again after Step 6 (clarification) to include security decisions and scope boundaries.bash .foundations/scripts/bash/create-new-feature.sh --json --issue $ISSUE_NUMBER --short-name "<module-name>" "<feature description>". Parse the JSON output to capture $BRANCH_NAME as $FEATURE and $DESIGN_FILE.tf-domain-category skillAskUserQuestion. Must include a security-defaults question.tf-module-research subagents for provider docs, AWS best practices, registry patterns, and edge cases. Wait for all to complete. Verify research files exist at specs/{FEATURE}/research-*.md via Glob.tf-module-design agent with FEATURE path and clarified requirements. The agent reads the constitution, design template, and research files from specs/{FEATURE}/research-*.md itself.specs/{FEATURE}/design.md exists via Glob. Re-launch once if missing.## 1. Purpose through ## 7. Open Questions). Fix inline if any missing.AskUserQuestion: input/output counts, resource count, security controls, test scenarios, checklist items. Options: approve, review file first, request changes.Design approved at specs/{FEATURE}/design.md. Run /tf-module-implement $FEATURE to build.