メニュー
Create a new task with auto-numbering. Use when creating new tasks to track work.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when manually generating or updating the canonical 3-workflow GitHub Actions CI/CD set (deploy.yml, provision.yml, post-merge-deploy.yml) for a Node.js + React application deployed to a VM via Terraform and Docker Compose. Also use when an operator invokes /cicd.generate, or when updating existing workflows to match project conventions. In `smaqit.new-greenfield-project`, the deployment agent generates workflows during Phase 5 using these patterns as reference — invoke this skill directly only when generating CI/CD outside the zero-to-prod flow. Note: `copilot-setup-steps.yml` is provided by the smaqit framework and is not generated by this skill.
Use when deploying a Node.js backend + React frontend application to a remote VM via rsync. Used in the Phase 5 dev environment sweep of `smaqit.new-greenfield-project` to validate the deployment approach locally before CI/CD. Also use as a manual fallback for direct VM deployment outside the CI/CD pipeline.
Use after any deployment to confirm the application is healthy before closing the task or proceeding. Checks the health endpoint, verifies the deployed commit SHA against the current local commit, and validates the SPA root HTTP response. Produces a PASS/FAIL report per check with a final summary. Also use when a deployment task asks to confirm success or when re-verifying after a fix.
Use when configuring a custom domain with a Let's Encrypt TLS certificate for a running nginx server. Covers DNS propagation verification, nginx server_name update, Certbot certificate issuance, HTTPS smoke tests, and auto-renewal verification. Also use when activating a purchased domain for a deployed application, setting up HTTPS post-deployment, or when a spec references INF-TOPOLOGY-004 through INF-TOPOLOGY-007 as pending TLS configuration.
Use when writing deploy stamp files (DEPLOY_SHA, DEPLOY_TIME) to the VM after a successful deployment, or when re-stamping without a full redeploy. Also use when the health endpoint returns "sha":"unknown" after deployment, when a deployed PR needs a notification comment, or when smaqit.infrastructure-deploy-rsync invokes the post-deploy stamp step. Produces DEPLOY_SHA and DEPLOY_TIME files in /opt/him/backend/ on the VM and optionally posts a deploy comment on the merged PR.
Use when validating staged files before committing to catch .env files, plaintext API keys/secrets, draft spec files on main-branch commits, and large files over 1 MB. Also use when setting up the automated git pre-commit hook via the bundled install script so checks run automatically on every commit. Produces a PASS/FAIL report per check, with filenames and matching lines listed for failures.
| name | smaqit.task-create |
| description | Create a new task with auto-numbering. Use when creating new tasks to track work. |
| metadata | {"version":"0.5.0"} |
Create a new task with the format: task.create [title] or task.create [title] - [description] - [criteria]
.smaqit/tasks/ directory.smaqit/tasks/NNN_task_title.md (NNN = next available number, zero-padded to 3 digits)**Status:** Not Started**Created:** YYYY-MM-DD (today)## Known Issues Triage placeholder note (for smaqit.task-start to overwrite)## Findings placeholder categories with TBD bullets (for smaqit.task-complete to overwrite).smaqit/tasks/PLANNING.md with status "Not Started"store_memory tool:
subject: "task state"fact: "[NNN] [Title] — Not Started (created YYYY-MM-DD)" (≤ 200 chars)citations: path to the task file just created (e.g., .smaqit/tasks/NNN_task_title.md)reason: "Ensures new task is visible in any branch without reading files, supporting parallel agent workflows"task.create Fix RAG chunking - Title only (prompt for details or infer from context)task.create Fix RAG chunking - Chunks are too large for embedding model - Title + descriptiontask.create Fix RAG chunking - Chunks too large - Chunks under 512 tokens, Tests pass - Full specificationUse assets/TASK_TEMPLATE.md as the canonical task file structure for task creation.
Fields populated at creation time: Status (set to Not Started) and Created (set to today's date). Fields such as Mode, Started, and Completed are omitted at creation and added later by the relevant skill as the task progresses.
Remember: .smaqit/tasks/PLANNING.md contains status of all tasks (sorted by ID) and is the single source of truth for task overview.