StackShift Implement FAQs

Question 1

What is the primary purpose of the StackShift Implement skill?

Accepted Answer

It automates the process of building missing features based on specifications located in the specs/ directory, ensuring 100% alignment with defined acceptance criteria.

Question 2

Is the implementation process fully automated?

Accepted Answer

While it automates code generation and testing, it includes checkpoints where the user must review generated code before commits and confirm transitions between implementation phases.

Question 3

How does it track progress across different sessions?

Accepted Answer

The skill uses a .stackshift-state.json file to record implementation progress, current phases, and completed features, allowing the developer to resume work exactly where they left off.

Question 4

What happens if the generated code doesn't match the specification?

Accepted Answer

The /speckit.analyze command identifies discrepancies. You can then choose to fix the implementation to match the spec or update the spec if requirements evolved during development.

Question 5

Does this skill require a specific directory structure?

Accepted Answer

Yes, it follows a convention using specs/ for requirements, docs/gap-analysis-report.md for roadmaps, and operations/ for error recovery procedures.

StackShift Implement

Key Features

Use Cases

StackShift Implement

Key Features

Use Cases