sociuu-task

Sociuu Task

Follow the team product task record standard. This skill is its agent procedure; human developers follow the same standard without installing it.

Use this skill for Apex, Fuse, or Prime changes. For Dock, GitOps, Admin, or other repositories, use it only when tracking is useful or an existing product task already owns the change. Inspect current ClickUp operations and fields. Search by supplied task ID, source report, feature and existing MR links before creating anything. Reuse a unique match; ask only when identity or scope conflicts. Investigation-only requests do not authorize task mutations.

Task and documents

Before implementation, establish scope, acceptance criteria, affected repositories, source links and known unknowns. Preserve human descriptions and ownership. Choose the list from the request, then from the shared standard's routing and your own instructions; ask only when neither decides. Query actual statuses and fields rather than guessing IDs.

Find the task's existing Ledger and QA Runbook through its description and attachments. Create missing records using task-documents.md. They are canonical in ClickUp for every tracked implementation, bug, maintenance or infrastructure task. A QA Runbook always exists, including explicit QA-not-applicable rationale and substitute verification. Small tasks may use named Ledger and QA Runbook sections in one canonical artifact; preserve existing separate documents. Do not create an independent task ledger per repository.

Maintain a clearly named Links & artefacts section in the main task description. Include every participating MR, Figma/Figma Make reference, Ledger, QA Runbook, and relevant ADR, context or other artifact. Preserve the rest of the description and verify each link identifies the intended resource. Do not invent missing assets.

Task attachments are acceptable for Ledger and QA Runbook records. Identify the current version and distinguish superseded versions; preserve existing artifacts. Do not introduce or require ClickUp Docs. Existing Docs may remain linked without migration. Native Add links/sidebar associations are optional conveniences, never completion gates; do not require Computer Use to maintain them.

Maintain

Update at scope changes, meaningful implementation milestones, review, QA and handoff. Reuse fetched read-only context within a phase until it changes; freshness before a write remains required. Keep status truthful; an MR is not a release. Read current task and record content immediately before each update, preserve others' sections, and refetch after writing. If another contributor changes an overlapping section, reconcile or ask that owner; never replace it from a stale local copy. Use append for discrete ledger entries where practical. Do not claim API locking or concurrency guarantees that the connector does not provide.

Local Markdown required by CE is a working copy: include canonical artifact URL and fetch revision/date, synchronize edits before handoff, and retain an explicit unsynchronized flag when ClickUp is unavailable. Do not silently adopt two authoritative versions. Migrate an existing repository ledger only after reading its history and preserving its source link.

Link all participating MRs and relevant Figma, ADR, domain, test and QA artifacts. Do not fabricate missing assets or require an ADR for a trivial task. Return task/document URLs, synchronized state and concrete remaining gaps.