Skip to content
Discussion options

You must be logged in to vote

So there are basically two ways to handle this:

If your new features are pretty straightforward - just manually add tasks to the tasks.json file and manage the steps through template.json. This skips the whole planning phase.

If you need proper planning for the new features - delete the .codemachine folder and add your updated specs. It’ll start fresh from planning.

The thing is, codemachine is really built for massive codebases that take 8+ hours. Even adding new features is going to take a long time to implement with the current version.

We're planning to add dynamic sizing in 0.4.0 so it can better match the actual size of what you’re building.

The reason just extending specification.m…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by schovi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants