원클릭으로 Manus에서 모든 스킬 실행

meta-vibekanban-sync

스타1

포크0

업데이트2026년 3월 7일 06:16

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.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

ccsert

ccsert/meta-forge

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Meta VibeKanban Sync

Use this skill for the VibeKanban binding and issue synchronization workflow.

What this skill does

Resolves VibeKanban identifiers through MCP
Decides which identifiers are safe to backfill at the current stage
Syncs task-tree nodes into VibeKanban issues
Updates issue descriptions and issue-map mappings
Keeps relationship synchronization explicit and idempotent

Trigger rule

Use this skill whenever any of the following is true:

The user mentions VibeKanban, MCP, or issue-map
The user asks to backfill organization_id, project_id, or repo_id
The user asks to sync task-breakdown into issues
The user asks to create or update Epic / Feature / Story / Task nodes in VibeKanban

Required reads

Read these before acting:

playbooks/use-vibekanban-mcp.md
docs/vibekanban-mcp-idempotency.md
standards/task-relationship-model.md
docs/meta/issue-map.draft.yaml
docs/planning/task-breakdown.md

If present, also inspect:

docs/meta/project-manifest.draft.yaml
projects/registry.yaml

Workflow

Resolve identifiers through MCP list tools before using them
Backfill only the IDs that are valid for the current phase
Use scripts/backfill-vibekanban-ids.mjs to patch manifest and issue-map files
Use scripts/sync-task-breakdown-to-vibekanban.mjs to prepare node sync payloads
Use scripts/sync-issue-relationships.mjs to prepare relationship sync payloads
Update issue-map after successful create/update operations
Treat issue synchronization as partial until the intended node subset is fully mapped

Hard rules

Never invent VibeKanban IDs
Do not backfill repo_id before repository binding exists
Do not claim full task synchronization if only a seed subset is synced
Do not treat issue descriptions as compliant unless they pass task-description validation
Keep issue-map as the source of truth for local mapping state

Scripts

scripts/backfill-vibekanban-ids.mjs
scripts/sync-task-breakdown-to-vibekanban.mjs
scripts/sync-issue-relationships.mjs

References

references/id-resolution.md

이 저장소의 다른 Skills

같은 저장소

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-task-description

ccsert/meta-forge

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.

2026-03-071

name	meta-vibekanban-sync
description	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.

Meta VibeKanban Sync

Use this skill for the VibeKanban binding and issue synchronization workflow.

What this skill does

Resolves VibeKanban identifiers through MCP
Decides which identifiers are safe to backfill at the current stage
Syncs task-tree nodes into VibeKanban issues
Updates issue descriptions and issue-map mappings
Keeps relationship synchronization explicit and idempotent

Trigger rule

Use this skill whenever any of the following is true:

The user mentions VibeKanban, MCP, or issue-map
The user asks to backfill organization_id, project_id, or repo_id
The user asks to sync task-breakdown into issues
The user asks to create or update Epic / Feature / Story / Task nodes in VibeKanban

Required reads

Read these before acting:

playbooks/use-vibekanban-mcp.md
docs/vibekanban-mcp-idempotency.md
standards/task-relationship-model.md
docs/meta/issue-map.draft.yaml
docs/planning/task-breakdown.md

If present, also inspect:

docs/meta/project-manifest.draft.yaml
projects/registry.yaml

Workflow

Resolve identifiers through MCP list tools before using them
Backfill only the IDs that are valid for the current phase
Use scripts/backfill-vibekanban-ids.mjs to patch manifest and issue-map files
Use scripts/sync-task-breakdown-to-vibekanban.mjs to prepare node sync payloads
Use scripts/sync-issue-relationships.mjs to prepare relationship sync payloads
Update issue-map after successful create/update operations
Treat issue synchronization as partial until the intended node subset is fully mapped

Hard rules

Never invent VibeKanban IDs
Do not backfill repo_id before repository binding exists
Do not claim full task synchronization if only a seed subset is synced
Do not treat issue descriptions as compliant unless they pass task-description validation
Keep issue-map as the source of truth for local mapping state

Scripts

scripts/backfill-vibekanban-ids.mjs
scripts/sync-task-breakdown-to-vibekanban.mjs
scripts/sync-issue-relationships.mjs

References

references/id-resolution.md