القائمة
Use when work should be tracked with tc, including creating PRDs, tasks, handoffs, logs, and work products, or when preserving detailed outputs outside the chat context.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | task-copilot |
| description | Use when work should be tracked with tc, including creating PRDs, tasks, handoffs, logs, and work products, or when preserving detailed outputs outside the chat context. |
tc is the execution record. Use it instead of stuffing long plans or implementation logs into chat.
Use --json on commands that support it.
Preferred binary:
tc
Fallback:
./.venv-tc/bin/tc
Commands:
tc task get <taskId> --json
tc wp store --task <taskId> --type <type> --title "..." --content "..." --json
tc task update <taskId> --status completed --json
Prefer the importable APIs for batches:
python3 - <<'PY'
from tc.api import create_prd, create_task, transaction
from tc.db.connection import get_db, find_db_path
conn = get_db(find_db_path())
try:
with transaction(conn):
prd = create_prd(title="Example", conn=conn)
task = create_task(prd=prd["id"], title="Example task", conn=conn)
finally:
conn.close()
print(f"PRD-{prd['id']} TASK-{task['id']}")
PY
Use a separate cc.api block for memory or skill batches. Do not import tc.api and cc.api in the same Python block.
Implementation tasks that require verification should use metadata like:
{"requiresQa": true, "qaStatus": "pending"}
After QA approval, record qaStatus, qaWpId, and verifiedAt when possible. Use scripts/copilot-gate.sh to inspect the convention.
Create the missing planning records:
tc prd create --title "..." --content "..." --json
tc task create --prd <id> --title "..." --description "..." --json
Formal multi-phase initiative knowledge belongs in docs/40-initiatives/NN-slug/: goals, phase designs, decisions, validation evidence, and retrospectives. tc remains authoritative for live task state, dependencies, assignments, work products, and QA status.
Link the initiative README to its PRD and tasks. Do not reproduce a live task board in Markdown.
Store detailed output when:
Read references/work-product-types.md for type guidance.
For a large work product that benefits from token-free review, use
tc wp render <id> --html. The HTML is a rendering of the authoritative work
product, not a second source of task state.
UI Designer for software interfaces. Use for visual direction, hierarchy, typography, color, spacing, component composition, design systems, visual critique, and making an interface feel intentional before UI implementation.
UX Designer for software workflows. Use for interaction design, task flows, information architecture, page states, usability, accessibility flow, form behavior, empty/loading/error/success states, and making a service concept usable before visual design or implementation.
Use when you need the Codex Copilot equivalent of Claude Copilot /update-project: refresh a project-local Codex Copilot setup from the shared framework.
Use when you need specialist role guidance for architecture, engineering, QA, security, docs, devops, service design, UX, UI design, UI implementation, or industrial design in a Codex session or delegated subagent.
Use when you need the Codex Copilot equivalent of Claude Copilot /config: inspect or explain cc configuration, known references, paths, and environment hydration.
Use when you want to invoke codex-copilot specialist agents natively in Codex, either by selecting the right specialist skill for the main session or by mapping specialists onto real Codex spawned-agent roles for delegated work.