buildermethods · CasJam · Aug 19, 2025 · Aug 19, 2025
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -5,6 +5,32 @@ All notable changes to Agent OS will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.4.1] - 2025-08-18
+
+### Replaced Decisions with Recaps
+
+Earlier versions added a decisions.md inside a project's .agent-os/product/.  In practice, this was rarely used and didn't help future development.
+
+It's been replaced with a new system for creating "Recaps"—short summaries of what was built—after every feature spec's implementation has been completed.  Similar to a changelog, but more descriptive and context-focused.  These recaps are easy to reference by both humans and AI agents.
+
+Recaps are automatically generated via the new complete-tasks.md process.
+
+### Added Project-Manager Subagent
+
+A goal of this update was to tighten up the processes for creating specs and executing tasks, ensuring these processes are executed reliably.  Sounds like the job for a "project manager".
+
+This update introduces a new subagent (for Claude Code) called project-manager which handles all task completion, status updates, and reporting progress back to you.
+
+### Spec Creation & Task Execution Reliability Improvements
+
+Several changes to the instructions, processes, and executions, all aimed at helping agents follow the process steps consistently.
+
+- Consolidated task execution instructions with clear step-by-step processes
+- Added post-flight verification rules to ensure instruction compliance
+- Improved subagent delegation tracking and reporting
+- Standardized test suite verification and git workflow integration
+- Enhanced task completion criteria validation and status management
+
 ## [1.4.0] - 2025-08-17
 
 BIG updates in this one!  Thanks for all the feedback, requests and support 🙏
@@ -235,6 +261,7 @@ Follow these steps to update a previous version to 1.4.0:
 - Task management with TDD workflow
 - Spec creation and organization system
 
+[1.4.1]: https://github.com/buildermethods/agent-os/compare/v1.4.0...v1.4.1
 [1.4.0]: https://github.com/buildermethods/agent-os/compare/v1.3.1...v1.4.0
 [1.3.1]: https://github.com/buildermethods/agent-os/compare/v1.3.0...v1.3.1
 [1.3.0]: https://github.com/buildermethods/agent-os/compare/v1.2.0...v1.3.0

diff --git a/claude-code/agents/project-manager.md b/claude-code/agents/project-manager.md
@@ -0,0 +1,42 @@
+---
+name: project-manager
+description: Use proactively to check task completeness and update task and roadmap tracking docs.
+tools: Read, Grep, Glob, Write, Bash
+color: cyan
+---
+
+You are a specialized task completion management agent for Agent OS workflows. Your role is to track, validate, and document the completion of project tasks across specifications and maintain accurate project tracking documentation.
+
+## Core Responsibilities
+
+1. **Task Completion Verification**: Check if spec tasks have been implemented and completed according to requirements
+2. **Task Status Updates**: Mark tasks as complete in task files and specifications
+3. **Roadmap Maintenance**: Update roadmap.md with completed tasks and progress milestones
+4. **Completion Documentation**: Write detailed recaps of completed tasks in recaps.md
+
+## Supported File Types
+
+- **Task Files**: .agent-os/specs/[dated specs folders]/tasks.md
+- **Roadmap Files**: .agent-os/roadmap.md
+- **Tracking Docs**: .agent-os/product/roadmap.md, .agent-os/recaps/[dated recaps files]
+- **Project Files**: All relevant source code, configuration, and documentation files
+
+## Core Workflow
+
+### 1. Task Completion Check
+- Review task requirements from specifications
+- Verify implementation exists and meets criteria
+- Check for proper testing and documentation
+- Validate task acceptance criteria are met
+
+### 2. Status Update Process
+- Mark completed tasks with [x] status in task files
+- Note any deviations or additional work done
+- Cross-reference related tasks and dependencies
+
+### 3. Roadmap Updates
+- Mark completed roadmap items with [x] if they've been completed.
+
+### 4. Recap Documentation
+- Write concise and clear task completion summaries
+- Create a dated recap file in .agent-os/product/recaps/
diff --git a/commands/create-tasks.md b/commands/create-tasks.md
@@ -0,0 +1,6 @@
+# Create Tasks
+
+Create a tasks list with sub-tasks to execute a feature based on its spec.
+
+Refer to the instructions located in this file:
+@.agent-os/instructions/core/create-tasks.md
diff --git a/config.yml b/config.yml
@@ -3,7 +3,7 @@
 # Refer to the official Agent OS documentation at:
 # https://buildermethods.com/agent-os
 
-agent_os_version: 1.4.0
+agent_os_version: 1.4.1
 
 agents:
   claude_code:

diff --git a/instructions/core/analyze-product.md b/instructions/core/analyze-product.md
@@ -78,9 +78,7 @@ Use the context-fetcher subagent to supplement codebase analysis with business c
 
   3. **Roadmap**: What features are planned next? Any major refactoring planned?
 
-  4. **Decisions**: Are there important technical or product decisions I should document?
-
-  5. **Team Preferences**: Any coding standards or practices the team follows that I should capture?
+  4. **Team Preferences**: Any coding standards or practices the team follows that I should capture?
 </context_questions>
 
 <instructions>
@@ -145,11 +143,6 @@ Refine the generated documentation to ensure accuracy for the existing product b
     - Add any missing infrastructure details
     - Document actual deployment setup
   </tech_stack_verification>
-  <decisions_documentation>
-    - Add historical decisions that shaped current architecture
-    - Document why certain technologies were chosen
-    - Capture any pivots or major changes
-  </decisions_documentation>
 </customization_tasks>
 
 <roadmap_template>
@@ -220,31 +213,6 @@ Verify installation completeness and provide clear next steps for the user to st
 
 </process_flow>
 
-## Error Handling
-
-<error_scenarios>
-  <scenario name="no_clear_structure">
-    <condition>Cannot determine project type or structure</condition>
-    <action>Ask user for clarification about project</action>
-  </scenario>
-  <scenario name="conflicting_patterns">
-    <condition>Multiple coding styles detected</condition>
-    <action>Ask user which pattern to document</action>
-  </scenario>
-  <scenario name="missing_dependencies">
-    <condition>Cannot determine full tech stack</condition>
-    <action>List detected technologies and ask for missing pieces</action>
-  </scenario>
-</error_scenarios>
-
-## Execution Summary
-
-<final_checklist>
-  <verify>
-    - [ ] Codebase analyzed thoroughly
-    - [ ] User context gathered
-    - [ ] plan-product.md executed with proper context
-    - [ ] Documentation customized for existing product
-    - [ ] Team can adopt Agent OS workflow
-  </verify>
-</final_checklist>
+<post_flight_check>
+  EXECUTE: @.agent-os/instructions/meta/post-flight.md
+</post_flight_check>