ICM Structure with Coding Projects

How are you guys using ICM folders to do development? ICM architecture works great with repeated tasks but programming a project requires a long list of different features (backend, frontend, art assets, etc). My main ICM uses now are a /feature-intake that writes implementation specs to a roadmap.md, /needs-review, and a decision-log.md (the index for a bigger historical decision-log-detailed.md).

What I'd ideally want longterm is an ICM folder working as a development studio; I give a high level request in a document (e.g., I want to create a mobile app that [does xyz]", then it reviews->brainstorms, finds courses of action->specs it out->develops->reviews->final corrections.

Just curious how everyone else is building projects with ICM.

15 comments

ICM Structure with Coding Projects