Where’s the architect…

[erapade]

Looks like we left out the architectural part in using the spec kit, and there's newer a re-architectural decision (leading to refactoring) when adding new features. We all know where this will take us...

If we add something similar to this to the constitution we could squeeze in the architect but it might also need an optional separate prompt like /architect.

Add a mandatory System Architecture section to SpecKit’s constitution for every project. Include: 1) Core modules and their interactions, 2) Data flow and storage strategy, 3) API/interface specs, 4) Scalability and fault tolerance goals, 5) Tech stack (languages, frameworks, DBs, APIs). Format in Markdown with a Mermaid diagram for clarity. Prioritize modularity, block feature creep, and enforce: When new user stories or features (>medium complexity) are added, AI must halt implementation, output an architecture diff highlighting changes or risks, and suggest updates-don’t proceed till reviewed. Auto-open a review ticket in the issue tracker for team/architect sign-off if needed. Reference this section on every spec update to keep design cohesive.