Code Implementation (Gate 0) FAQs

Question 1

How are 'Exploratory Spikes' handled?

Accepted Answer

Spikes are 60-minute time-boxed sessions for learning. All code generated during a spike must be deleted after the session to ensure the final implementation is built cleanly via TDD.

Question 2

What does 'Gate 0' mean in this skill?

Accepted Answer

Gate 0 refers to the initial development phase where code is implemented. This skill ensures that all work in this phase follows project standards and TDD before proceeding to review.

Question 3

What happens if the skill cannot detect the project language?

Accepted Answer

Instead of assuming a default language, the skill will prompt the user to select the correct specialized agent to prevent applying the wrong architectural patterns.

Question 4

Does this skill support multi-language projects?

Accepted Answer

Yes, it automatically detects the language via file patterns, go.mod, or package.json, and selects the appropriate agent for Go, TypeScript, or Frontend work.

Question 5

Why does the skill require deleting code if a test wasn't written first?

Accepted Answer

To prevent 'testing-after,' which often leads to biased tests. Deleting and restarting with a failing test ensures the code is truly test-driven and maintainable.

Code Implementation (Gate 0)

Key Features

Use Cases

Code Implementation (Gate 0)

Key Features

Use Cases