docker/skills-cache/tf-module-plan/SKILL.md
SDD Phases 1-2. Clarify requirements, research, produce design.md, and await human approval before any code is written.
npx skillsauth add agentdevsl/agentpane tf-module-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
development
AWS security assessment domains, risk rating framework, CIS/NIST reference baselines, and evidence-based finding format. Use when reviewing AWS security posture, assessing risk, or applying CIS/NIST baselines to Terraform configurations.
testing
--- name: "tf-runtask" description: "Retrieve and display Terraform Cloud/Enterprise run task results for a given run. Use this skill whenever the user asks about run task results, run task checks, task stage statuses, or wants to inspect what run tasks reported for a Terraform Cloud/Enterprise run. Triggers on phrases like "check the run tasks", "what did the run tasks say", "show run task results", "get task results for run-xxx", or any reference to run task outcomes on a specific run." source
devops
Research strategies for AWS documentation, provider docs, and public registry patterns. Use when researching AWS services, investigating provider resources, or studying public registry modules for design patterns.
development
Validation results summary template for Phase 4 output. Provides the format for reporting terraform test, validate, fmt, tflint, pre-commit, trivy, and security checklist results.