aibdd-carry-on-engineering-plan

Coordinate phased engineering plans with human-in-the-loop reviews and dependency graphs.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/zenbuapps/zenbu-powers --skill aibdd-carry-on-engineering-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aibdd-carry-on-engineering-plan
Source: https://github.com/zenbuapps/zenbu-powers/tree/main/skills/aibdd-carry-on-engineering-plan
Command: npx skills add https://github.com/zenbuapps/zenbu-powers --skill aibdd-carry-on-engineering-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

逐步執行工程計畫,搭配 human-in-the-loop 審查。每個 Phase 由對應 skill 連續執行所有內部步驟,完成後展示交付物進入 feedback loop。使用者審查通過後才推進至下一個 Phase。支援資料夾結構(plan.md + todo/doing/done/)與 Dependency Graph,允許多個 AI 平行執行互不依賴的 Phase。當使用者說「carry on engineering plan」「carry on」「繼續工程計畫」或想恢復執行先前擬定的工程計畫時觸發。

Core Features & Use Cases

  • Phase-by-Phase execution with human-in-the-loop reviews and automatic phase-transition based on user sign-off.
  • Dependency graph aware orchestration across multiple AI agents with parallelism and strict phase sequencing.
  • Feedback loop for deliverable reviews and LGTM-based sign-offs, with Consistency Check and audit trails.

Quick Start

開始執行工程計畫,請根據 plan.md 的依賴圖與 todo/doing/done 結構自動啟動第一個 Phase。

Frequently Asked Questions about aibdd-carry-on-engineering-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute an engineering plan with human-in-the-loop reviews?

To execute an engineering plan with human-in-the-loop reviews, this Skill coordinates phased deliverables, requiring user LGTM sign-off before advancing. It enforces dependency constraints and uses a plan.md file with todo/doing/done folders for artifact tracking.

Can I run multiple AI agents in parallel during phase management?

Yes, you can run multiple AI agents in parallel during phase management. The Skill uses a dependency graph to orchestrate parallel execution of non-dependent phases while strictly sequencing dependent phases across multiple AI agents.

How does dependency graph orchestration work for engineering plans?

Dependency graph orchestration maps phase relationships to enforce strict sequencing and allow parallelism. It ensures dependent phases wait for sign-off while non-dependent phases run simultaneously across multiple AI agents.

What is the best way to track deliverables and ensure auditability in engineering plans?

The best way to track deliverables and ensure auditability is by using plan.md immutability alongside a todo/doing/done folder structure. This provides absolute-path artifact tracking, consistency checks, and LGTM-based sign-off audit trails.

How do I trigger the continuation of a previously drafted engineering plan?

To trigger the continuation of a previously drafted engineering plan, simply say 'carry on engineering plan', 'carry on', or 'continue engineering plan'. The Skill resumes execution from the plan.md dependency graph and folder structure.

Do I need a specific folder structure to manage engineering plan phases?

Yes, you need a folder structure containing plan.md and todo/doing/done directories to manage engineering plan phases. This structure enables automatic phase-transition, absolute-path artifact tracking, and strict phase progression.