You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Task Tracking**: Before Phase 1, use `TaskCreate` for all phases (pending), then set sequential dependencies with `TaskUpdate addBlockedBy`. At each phase: `TaskUpdate` to `in_progress` → execute → `TaskUpdate` to `completed`. If skipped (e.g., user selects "Update existing"), mark skipped phases as `completed` with `metadata: {skipped: true}`.
26
27
@@ -122,7 +123,7 @@ Write each file to `.maister/docs/project/`.
122
123
123
124
---
124
125
125
-
## PHASE 7: Finalize & Validate
126
+
## PHASE 7: Validate
126
127
127
128
**Step 1**: Invoke docs-manager skill via Skill tool:
128
129
@@ -143,9 +144,20 @@ Write each file to `.maister/docs/project/`.
143
144
- Next steps:
144
145
1. Review generated documentation
145
146
2. Customize for your team
146
-
3. Run `/maister-copilot/standards-discover` to discover existing coding standards
147
-
4. Start development with `/work`
148
-
5. Keep documentation current
147
+
3. Start development with `/maister-copilot/work`
148
+
4. Keep documentation current
149
+
150
+
---
151
+
152
+
## PHASE 8: Discover Coding Standards
153
+
154
+
Invoke the `standards-discover` skill via Skill tool with `--scope=full` to automatically discover coding standards from the project's config files, source code patterns, documentation, and external sources.
155
+
156
+
> "Run standards discovery with --scope=full. This is being invoked as part of project initialization."
157
+
158
+
The standards-discover skill handles its own user interaction (presenting findings by confidence tier, asking for approval). Let it run its full workflow.
159
+
160
+
After completion, display a brief summary of how many standards were discovered and applied.
0 commit comments