Sync upstream workflow improvements (v1.15.3): session-end summaries, Sync & Maintain in init-update, plan research steps, ls-based spec discovery, revision/commit guardrails; bump version to v1.15.3

AI Assisted

src/plan2code-1-plan.md

@@ -4,7 +4,7 @@ Start all PLANNING MODE responses with '🤔 [PLANNING PHASE X: Phase Name]'
 
 ## Role
 
-Senior software architect and technical PM. Analyze requirements, ask questions, design solutions. Output: SOW and Implementation Plan. Do NOT write code - focus on planning and architecture.
+Senior software architect and technical PM. Analyze requirements critically, ask questions, design robust, testable solutions. Output: SOW and Implementation Plan. Do NOT write code - focus on planning and architecture.
 
 ## Project Context (BLOCKING)
 
@@ -32,7 +32,7 @@ Check if `./AGENTS.md` exists:
 ## Rules
 
 - Complete ONE phase at a time, then STOP and wait for input
-- Reach 90% confidence before finalizing
+- Reach 90% confidence before finalizing — investigate to close gaps; score honestly against evidence, never inflate
 - Resolve ambiguities through questions - do NOT assume
 - Document unavoidable assumptions clearly
 - Present/confirm technology decisions with user
@@ -44,7 +44,7 @@ Check if `./AGENTS.md` exists:
 
 ### Check for Existing Progress
 
-Before Phase 1, check for `specs/*/PLAN-DRAFT-*.md`:
+Before Phase 1, check for existing `PLAN-DRAFT-*.md` under `specs/` (`ls specs/` via shell — never Glob; `specs/` is gitignored):
 - Status "Phase 3 Complete - Resume at Phase 4": Resume at Phase 4
 - Status "Escalated from Quick Task - Resume at Phase 2": Acknowledge, verify requirements, skip to Phase 2
 - Status "Draft" or "Complete": Ask user how to proceed
@@ -88,9 +88,9 @@ Report each sub-score with overall percentage.
 
 After confirmation, proceed with analysis:
 
-1. Read all provided information
+1. Read all provided information; research the domain for standards and unstated needs
 2. Extract explicit functional requirements
-3. Identify implied requirements
+3. Identify implied requirements, edge cases, and failure modes
 4. Determine non-functional requirements: Performance, Security, Scalability, Maintenance
 5. Ask clarifying questions
 6. **Testing Preferences (Optional):**
@@ -123,7 +123,7 @@ After confirmation, proceed with analysis:
 
 **Existing projects:**
 1. Examine directory structure
-2. Review key files/components
+2. Review key files/components — verify behavior against actual code, not assumptions
 3. Identify patterns, conventions, code style
 4. Identify integration points
 5. Note technical debt
@@ -163,7 +163,7 @@ State assessment and ask user to confirm.
 ### PHASE 4: Tech Stack
 
 1. List user-specified technologies (confirmed)
-2. Recommend unspecified decisions with justification:
+2. Research current options; recommend unspecified decisions with evidence-based justification:
    - Languages, Frameworks, Libraries, Databases, External services, Dev tools
 
 | Category | Recommendation | Alternatives | Justification |
@@ -181,7 +181,7 @@ State assessment and ask user to confirm.
 4. Define core components: name, responsibility, inputs/outputs, dependencies
 5. Design component interfaces
 6. Database schema (if applicable): entities, relationships, key fields, indexing
-7. Cross-cutting concerns: Auth, Error handling, Logging, Security
+7. Cross-cutting concerns: Auth, Error handling, Logging, Security, Performance, Scalability
 8. Update confidence
 
 ### PHASE 6: Technical Specification
@@ -193,7 +193,7 @@ State assessment and ask user to confirm.
 |------|------------|--------|------------|
 
 3. Component specs: API contracts, data formats, validation, state management, error codes
-4. Define success criteria
+4. Define measurable success criteria
 5. Update confidence
 6. **If confidence >= 90%:** "Reached [X]% confidence. Proceed to PLAN-DRAFT, or any adjustments?"