Conductor Implement Engine FAQs

Question 1

How does it track my progress throughout a project?

Accepted Answer

It continuously synchronizes task statuses between the active session and your plan.md file, updating tasks from pending to in-progress, completed, or blocked in real-time.

Question 2

What is the Phase Completion Protocol?

Accepted Answer

It is a 10-step verification process triggered at the end of a project phase that ensures test coverage meets requirements, automated tests pass in CI mode, and the user provides manual verification before a checkpoint is created.

Question 3

What is the TDD cycle used by the implement skill?

Accepted Answer

The skill follows a strict Red/Green/Refactor methodology: you must first write a failing test, then write the minimum code required to pass the test, and finally refactor the code for quality while ensuring tests stay green.

Question 4

Can I work on multiple tasks simultaneously?

Accepted Answer

To ensure focus and quality, the skill enforces a 'One Task at a Time' principle, requiring the current task to be fully completed or marked as blocked before moving to the next one.

Question 5

Does this skill help with Git commit messages?

Accepted Answer

Yes, it automates structured commits using standardized types like feat, fix, and refactor. It also attaches Git Notes to each commit to provide a deep audit trail of what was changed and why.

Conductor Implement Engine

소개

주요 기능

사용 사례

Conductor Implement Engine

소개

주요 기능

사용 사례