workflows

原文涵盖的主题

• Workflows for AI-assisted development
• Table of contents
• Complexity detection
• LOW complexity (Quick Fix)
• MEDIUM complexity
• HIGH complexity
• Problem type routing (Quick Reference)
• Branch strategy

Complexity detection LOW complexity (Quick Fix) MEDIUM complexity HIGH complexity Problem type routing (Quick Reference) Branch strategy The spec workflows See also -- Principle: Match the scope of the documentation to the complexity of the task. Grading: the grade is set once the code has been read, by the risk of the change. The criteria and two worked examples are in aide-analyze's complexity-and-analysis.md, section "Classification", and nowhere else. Each level below says what its grade means for the analysis and for the documents. Analysis scope: Read ONLY the mentioned file Documentation: Short and concise (< 200 lines total) Estimate: Minutes to hours (< 2 hours) -- Analysis scope: Find files related to the component/module Find related tests and usage sites, and stop there Documentation: Moderate detail (100-300 lines total) Estimate: Hours to days (2-16 hours) -- Analysis scope: Search the codebase broadly for patterns Categorize files by complexity Analyze API impact (frontend - backend) Identify edge cases and risks Documentation: Comprehensive analysis (300-800 lines total) Estimate: Days to weeks (1-10 days) -- Start every problem type from the project's OWN documenta

这里只展示节选，请以完整原文和当前要求为准。