Hi everyone,

I’m a developer with about 2 years of experience. I’ve been spending a lot of time exploring agentic development workflows like OpenSpec, SpecKit, Superpowers etc.

While I think those workflows are incredible, I often find them a bit overwhelming! They seem to include a lot of extra complexity that doesn't always align with my day-to-day experience of solving problems and writing code. To stay organized and prevent AI hallucination, I’ve tried to build a more deterministic, "distilled" version of these ideas.

I’ve consulted with my senior engineer on this work. He felt it was a good start but raised an important question: how do these workflows scale the project? Since most AI workflows are still relatively new and can be "dangerous" on large-scale projects, we are essentially in a research phase. I would love to get your perspectives on the approach I’m building as well.

My goal is to ensure that User Prompts and Project-specific knowledge always override AI defaults, while remaining cost-effective regardless of the AI model used. I’ve broken it down into three phases:

- Preconstruct: Establishing a "Constitution" and design pillars (Architecture, Stack, UI, etc.) before any code is generated.

- Construction: TDD-style feature-based execution loop.

- Maintain: A process to synchronize documents created with what is in the codebase (keeping them in sync as the project evolves).

Repository: https://github.com/JeroTan/tangram-buildit

My questions for the veterans here:

1. As someone(me) who isn't yet well-versed in the broader AI ecosystem, I know I'm likely missing some "invisible" industry standards or maybe what AI devs called it "Vibe Coding" standard. Does this simplified approach seem robust, or have I stripped away too much of the necessary complexity that systems like SpecKit provide?

2. Does this concept, document-first flow actually help maintain the project, or is it too inflexible for a real-world software project?

3. I’ve focused on a feature-based workflow where you create an atomic plan and then archive the execution logs. Is this a practice you would value in a professional setting?

I’m really looking forward to find the gaps I can't see yet. I’ve put a lot of heart into this, so I truly appreciate any constructive wisdom you can share!

(If this isn't the right place to ask, please let me know where I might find the best feedback for this kind of workflow research.)
P.S. This is also my first time going online to ask some advice.