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.

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.

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.

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.

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.

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.