メニュー
Create a local task draft for review before uploading. Use when user says "draft task", "create task draft", "task-draft", "new task", or "plan a task".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generate a Gemini text-to-speech audio file for each narrative-style .md file in a directory tree, and attach a Listen link at the top of every file. Strips ASCII diagrams, navigation, and separators before synthesis — only paragraph prose is spoken. Use when user says "generate story audio", "text to speech for stories", "tts for markdown", "attach audio to stories", or "local-audio".
End-to-end ERP marketing article workflow — fetch today's marketing task, write the article with diagram and translations, upload to production, and mark the task as completed. Use when user says "marketing article", "erp marketing", "write today's marketing article", or "local-erp-marketing-article".
Assign the next 5 unchecked ERP features from data/erp_features.md as ERP Marketing tasks, distributed one per weekday (Mon–Fri) of the coming week. Use when user says "weekly assignment", "assign marketing tasks", "erp marketing weekly", or "local-erp-marketing-article-weekly-assignment".
Bulk-like posts on the TadReamk LinkedIn company page feed. Navigates to the admin feed, injects a JS script that likes posts with random delays, scrolls to load more, and monitors until the target count is reached. Use when user says "linkedin like", "like linkedin posts", "bulk like", or "local-erp-marketing-linkedin-like".
Generate a narrative user-story documentation set from a customer-requirement share URL. Fetches the document, saves it under data/customer_requirements/ as requirements.md (or requirements_cn.md + requirements_en.md if Chinese), then turns each feature into a human-centred, diagram-driven chapter under narrative_user_story/. Use when user says "generate narrative user story", "write narrative user story", "narrative story from requirements", "narrative docs", or "local-generate-narrative-user-story".
Sync the local .claude.prod/api_doc/ directory with the latest API documentation from the fullstack ERP project. Use when user says "update api doc", "sync api doc", "refresh api doc", or "api-doc-update".
| name | task-draft |
| description | Create a local task draft for review before uploading. Use when user says "draft task", "create task draft", "task-draft", "new task", or "plan a task". |
Create a local task draft for review before uploading.
This command requires user input describing the task (title, what it's about, etc.).
Username is loaded from the TASK_USERNAME variable — first from .env in the current working directory, then from ~/.claude/.env as a global fallback. This user will be the manager of the task.
Load the username by reading .env in the current working directory and extracting the TASK_USERNAME value. If the variable is missing or empty, try ~/.claude/.env as a fallback. If still missing in both locations, tell the user to set it in either .env (project-level) or ~/.claude/.env (global) and stop.
From the user's input (provided as the command argument), determine:
low, medium, high, urgent, critical. Default to medium unless the user indicates urgency.Ask the user which project this task belongs to. Fetch the active projects list:
curl -s "https://api-erp.tadreamk.com/api/v1/task-projects/active-list" \
-H "Authorization: Bearer <token>"
Load the auth token from WEBAPP_ACCESS_TOKEN — first from .env in the current working directory, then from ~/.claude/.env as a fallback.
Present the projects as options for the user to pick from, plus a "None" option for no project.
Generate a slug from the title: lowercase, replace spaces and special chars with hyphens, remove consecutive hyphens, trim to reasonable length. Prefix with {YYMMDD}_{HHMM}_ using the current date and time. Example: "Create a list of commands" at 2026-03-04 15:30 becomes 260304_1530_create-a-list-of-commands.
Create a Markdown draft file at data/tasks/<YYMMDD_HHMM_slug>.md with:
# <title>
- **Priority**: <priority>
- **Status**: in_queue
- **Start date**: <today's date YYYY-MM-DD>
- **Project**: <project title or "None">
- **Project ID**: <project id or "None">
- **Manager**: <TASK_USERNAME>
## Description
<brief summary sentence>
- <key item or subtask>
- <key item or subtask>
- ...
Create the data/tasks/ directory if it doesn't exist.
If data/tasks/<YYMMDD_HHMM_slug>.md already exists, ask the user whether to overwrite or save as <YYMMDD_HHMM_slug>_<N>.md (increment N).
Show the draft summary:
Task draft saved to data/tasks/<YYMMDD_HHMM_slug>.md
Title: <title>
Priority: <priority>
Project: <project title or "None">
Manager: <TASK_USERNAME>
To upload this task, run /task-add