Run any Skill in Manus with one click

meta-task-description

Stars1

Forks0

UpdatedMarch 7, 2026 at 06:16

Render and validate VibeKanban issue descriptions so they comply with this meta-repo's task description protocol. Use this skill whenever creating or updating executable tasks, checking whether a ready task description is compliant, syncing tasks into VibeKanban, or when the user asks whether a task description follows the meta-repo requirements.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ccsert

ccsert/meta-forge

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

LogisticiansBusiness and Financial Operations Occupations·SOC 13-1081

File Explorer

4 files

SKILL.md

readonly

name	meta-task-description
description	Render and validate VibeKanban issue descriptions so they comply with this meta-repo's task description protocol. Use this skill whenever creating or updating executable tasks, checking whether a ready task description is compliant, syncing tasks into VibeKanban, or when the user asks whether a task description follows the meta-repo requirements.

Meta Task Description

Use this skill to keep VibeKanban task descriptions structurally compliant.

What this skill does

Renders issue descriptions using the meta-repo task description structure
Validates whether an issue description contains the required fields
Distinguishes executable leaf tasks from container nodes like epic/feature/story
Prevents ready-task descriptions from drifting into incomplete free-form summaries

Trigger rule

Use this skill whenever either of the following is true:

A VibeKanban issue is being created or updated for a task in this meta-repo
The user asks whether a task description is compliant, complete, or ready for execution
A task is being marked or treated as workspace_launchable: true

Required reads

Read these before acting:

templates/vibekanban-issue-description.md
standards/task-description-protocol.md
standards/executable-task-policy.md
standards/task-execution-unit.md
docs/planning/task-breakdown.md

Workflow

Determine whether the node is epic, feature, story, or task
If executable, require the full execution classification and relationship fields
Run scripts/render-vibekanban-description.mjs to generate the structured description
Run scripts/validate-issue-description.mjs to check required fields
If validation fails, do not present the description as ready-task compliant

Hard rules

Any task intended for execution must include the required identity, execution, relationship, repo, input, goal, and acceptance fields
Free-form summary descriptions are not sufficient for workspace_launchable: true tasks
If required fields are missing, the task must be treated as non-compliant until corrected
Relationship indexes in the description must remain aligned with issue-map

Scripts

scripts/render-vibekanban-description.mjs
scripts/validate-issue-description.mjs

References

references/required-fields.md

More from this repository

same repository

meta-onboard-project

ccsert/meta-forge

Onboard an existing code repository into meta-forge management by producing an audit report, backfilling standard documents (project-definition, architecture, task-breakdown), registering in the project registry, and optionally binding to VibeKanban. Use this skill whenever the user wants to bring an existing project under meta-forge management, import a legacy codebase, or onboard a historical project that already has code but lacks meta-forge documentation.

2026-03-111

meta-new-project

ccsert/meta-forge

Drive a new project from idea to meta-repo document baseline by producing `project-definition.md`, `architecture-init.md`, and `task-breakdown.md` in the correct order with human gates between stages. Use this skill whenever the user is starting a new project, refining an initial idea into a structured project in the meta-repo, or wants to complete stage 1-3 of the new-project flow before bootstrap and VibeKanban binding.

2026-03-071

meta-project-bootstrap

ccsert/meta-forge

Create and bootstrap a business repository from the meta-repo: collect repository coordinates, create the GitHub repository, initialize the local repo, inject core design documents, and create manifest and issue-map primary copies. Use this skill whenever the user wants to create a new business repository, inject meta-repo docs, bootstrap a project after stage 1-3 are complete, or asks to perform stage 4/5 of the new-project flow.

2026-03-071

meta-stage-gate

ccsert/meta-forge

Determine the current project stage in this meta-repo, output a stage snapshot, and enforce stage boundaries before any next-step recommendation. Use this skill whenever the user asks things like "我们到哪一步了", "下一步是什么", "现在能不能开始执行", "阶段是否完成", or whenever the conversation is happening inside the meta-repo and there is any risk of jumping from planning, bootstrap, or VibeKanban sync directly into business-code execution.

2026-03-071

meta-vibekanban-sync

ccsert/meta-forge

Bind a project to VibeKanban, resolve and backfill MCP IDs, sync task breakdown nodes into VibeKanban issues, and keep issue-map metadata aligned. Use this skill whenever the user mentions VibeKanban, MCP, organization_id, project_id, repo_id, issue sync, issue-map backfill, or wants to create/update Epic/Feature/Story/Task nodes from the meta-repo into VibeKanban.

2026-03-071

name	meta-task-description
description	Render and validate VibeKanban issue descriptions so they comply with this meta-repo's task description protocol. Use this skill whenever creating or updating executable tasks, checking whether a ready task description is compliant, syncing tasks into VibeKanban, or when the user asks whether a task description follows the meta-repo requirements.

Meta Task Description

Use this skill to keep VibeKanban task descriptions structurally compliant.

What this skill does

Renders issue descriptions using the meta-repo task description structure
Validates whether an issue description contains the required fields
Distinguishes executable leaf tasks from container nodes like epic/feature/story
Prevents ready-task descriptions from drifting into incomplete free-form summaries

Trigger rule

Use this skill whenever either of the following is true:

A VibeKanban issue is being created or updated for a task in this meta-repo
The user asks whether a task description is compliant, complete, or ready for execution
A task is being marked or treated as workspace_launchable: true

Required reads

Read these before acting:

templates/vibekanban-issue-description.md
standards/task-description-protocol.md
standards/executable-task-policy.md
standards/task-execution-unit.md
docs/planning/task-breakdown.md

Workflow

Determine whether the node is epic, feature, story, or task
If executable, require the full execution classification and relationship fields
Run scripts/render-vibekanban-description.mjs to generate the structured description
Run scripts/validate-issue-description.mjs to check required fields
If validation fails, do not present the description as ready-task compliant

Hard rules

Any task intended for execution must include the required identity, execution, relationship, repo, input, goal, and acceptance fields
Free-form summary descriptions are not sufficient for workspace_launchable: true tasks
If required fields are missing, the task must be treated as non-compliant until corrected
Relationship indexes in the description must remain aligned with issue-map

Scripts

scripts/render-vibekanban-description.mjs
scripts/validate-issue-description.mjs

References

references/required-fields.md