{communication_language}stepsCompleted: [1] before loading next stepInitialize the Architecture workflow by detecting continuation state, discovering input documents, and setting up the document for collaborative architectural decision making.
First, check if the output document already exists:
*architecture*.mdIf the document exists and has frontmatter with stepsCompleted:
./step-01b-continue.md immediatelyIf no document exists or no stepsCompleted in frontmatter:
Discover and load context documents using smart discovery. Documents can be in the following locations:
Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for *foo*.md and not found, also search for a folder called foo/index.md (which indicates sharded content)
Try to discover the following:
*brief*.md)*prd*.md)*ux-design*.md) and other*research*.md){product_knowledge} or docs folder.)**/project-context.md)Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules
Loading Rules:
inputDocuments arrayBefore proceeding, verify we have the essential inputs:
PRD Validation:
Other Input that might exist:
Copy the template from {installed_path}/architecture-decision-template.md to {planning_artifacts}/architecture.md
Complete setup and report to user:
Document Setup:
{planning_artifacts}/architecture.md from templateInput Documents Discovered: Report what was found: "Welcome {{user_name}}! I've set up your Architecture workspace for {{project_name}}.
Documents Found:
Files loaded: {list of specific file names or "No additional documents found"}
Ready to begin architectural decision making. Do you have any other documents you'd like me to include?
[C] Continue to project context analysis
✅ Existing workflow detected and handed off to step-01b correctly
✅ Fresh workflow initialized with template and frontmatter
✅ Input documents discovered and loaded using sharded-first logic
✅ All discovered files tracked in frontmatter inputDocuments
✅ PRD requirement validated and communicated
✅ User confirmed document setup and can proceed
❌ Proceeding with fresh initialization when existing workflow exists ❌ Not updating frontmatter with discovered input documents ❌ Creating document without proper template ❌ Not checking sharded folders first before whole files ❌ Not reporting what documents were found to user ❌ Proceeding without validating PRD requirement
❌ CRITICAL: Reading only partial step file - leads to incomplete understanding and poor decisions ❌ CRITICAL: Proceeding with 'C' without fully reading and understanding the next step file ❌ CRITICAL: Making decisions without complete understanding of step requirements and protocols
After user selects [C] to continue, only after ensuring all the template output has been created, then load ./step-02-context.md to analyze the project context and begin architectural decision making.
Remember: Do NOT proceed to step-02 until user explicitly selects [C] from the menu and setup is confirmed!