Skip to content

Commit a976833

Browse files
CasJamCasJam
authored
Merge pull request #91 from buildermethods/task-execution
v1.4.1: project-manager subagent, improved create-spec and execute-tasks
2 parents d501619 + 9e5bbe4 commit a976833

16 files changed

Lines changed: 523 additions & 523 deletions

‎CHANGELOG.md‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,32 @@ All notable changes to Agent OS will be documented in this file.
55
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
66
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
77

8+
## [1.4.1] - 2025-08-18
9+
10+
### Replaced Decisions with Recaps
11+
12+
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.
13+
14+
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.
15+
16+
Recaps are automatically generated via the new complete-tasks.md process.
17+
18+
### Added Project-Manager Subagent
19+
20+
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".
21+
22+
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.
23+
24+
### Spec Creation & Task Execution Reliability Improvements
25+
26+
Several changes to the instructions, processes, and executions, all aimed at helping agents follow the process steps consistently.
27+
28+
- Consolidated task execution instructions with clear step-by-step processes
29+
- Added post-flight verification rules to ensure instruction compliance
30+
- Improved subagent delegation tracking and reporting
31+
- Standardized test suite verification and git workflow integration
32+
- Enhanced task completion criteria validation and status management
33+
834
## [1.4.0] - 2025-08-17
935

1036
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:
235261
- Task management with TDD workflow
236262
- Spec creation and organization system
237263

264+
[1.4.1]: https://github.com/buildermethods/agent-os/compare/v1.4.0...v1.4.1
238265
[1.4.0]: https://github.com/buildermethods/agent-os/compare/v1.3.1...v1.4.0
239266
[1.3.1]: https://github.com/buildermethods/agent-os/compare/v1.3.0...v1.3.1
240267
[1.3.0]: https://github.com/buildermethods/agent-os/compare/v1.2.0...v1.3.0

‎claude-code/agents/project-manager.md‎

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
---
2+
name: project-manager
3+
description: Use proactively to check task completeness and update task and roadmap tracking docs.
4+
tools: Read, Grep, Glob, Write, Bash
5+
color: cyan
6+
---
7+
8+
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.
9+
10+
## Core Responsibilities
11+
12+
1. **Task Completion Verification**: Check if spec tasks have been implemented and completed according to requirements
13+
2. **Task Status Updates**: Mark tasks as complete in task files and specifications
14+
3. **Roadmap Maintenance**: Update roadmap.md with completed tasks and progress milestones
15+
4. **Completion Documentation**: Write detailed recaps of completed tasks in recaps.md
16+
17+
## Supported File Types
18+
19+
- **Task Files**: .agent-os/specs/[dated specs folders]/tasks.md
20+
- **Roadmap Files**: .agent-os/roadmap.md
21+
- **Tracking Docs**: .agent-os/product/roadmap.md, .agent-os/recaps/[dated recaps files]
22+
- **Project Files**: All relevant source code, configuration, and documentation files
23+
24+
## Core Workflow
25+
26+
### 1. Task Completion Check
27+
- Review task requirements from specifications
28+
- Verify implementation exists and meets criteria
29+
- Check for proper testing and documentation
30+
- Validate task acceptance criteria are met
31+
32+
### 2. Status Update Process
33+
- Mark completed tasks with [x] status in task files
34+
- Note any deviations or additional work done
35+
- Cross-reference related tasks and dependencies
36+
37+
### 3. Roadmap Updates
38+
- Mark completed roadmap items with [x] if they've been completed.
39+
40+
### 4. Recap Documentation
41+
- Write concise and clear task completion summaries
42+
- Create a dated recap file in .agent-os/product/recaps/

‎commands/create-tasks.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
# Create Tasks
2+
3+
Create a tasks list with sub-tasks to execute a feature based on its spec.
4+
5+
Refer to the instructions located in this file:
6+
@.agent-os/instructions/core/create-tasks.md

‎config.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
# Refer to the official Agent OS documentation at:
44
# https://buildermethods.com/agent-os
55

6-
agent_os_version: 1.4.0
6+
agent_os_version: 1.4.1
77

88
agents:
99
claude_code:

‎instructions/core/analyze-product.md‎

Lines changed: 4 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -78,9 +78,7 @@ Use the context-fetcher subagent to supplement codebase analysis with business c
7878

7979
3. **Roadmap**: What features are planned next? Any major refactoring planned?
8080

81-
4. **Decisions**: Are there important technical or product decisions I should document?
82-
83-
5. **Team Preferences**: Any coding standards or practices the team follows that I should capture?
81+
4. **Team Preferences**: Any coding standards or practices the team follows that I should capture?
8482
</context_questions>
8583

8684
<instructions>
@@ -145,11 +143,6 @@ Refine the generated documentation to ensure accuracy for the existing product b
145143
- Add any missing infrastructure details
146144
- Document actual deployment setup
147145
</tech_stack_verification>
148-
<decisions_documentation>
149-
- Add historical decisions that shaped current architecture
150-
- Document why certain technologies were chosen
151-
- Capture any pivots or major changes
152-
</decisions_documentation>
153146
</customization_tasks>
154147

155148
<roadmap_template>
@@ -220,31 +213,6 @@ Verify installation completeness and provide clear next steps for the user to st
220213
221214
</process_flow>
222215
223-
## Error Handling
224-
225-
<error_scenarios>
226-
<scenario name="no_clear_structure">
227-
<condition>Cannot determine project type or structure</condition>
228-
<action>Ask user for clarification about project</action>
229-
</scenario>
230-
<scenario name="conflicting_patterns">
231-
<condition>Multiple coding styles detected</condition>
232-
<action>Ask user which pattern to document</action>
233-
</scenario>
234-
<scenario name="missing_dependencies">
235-
<condition>Cannot determine full tech stack</condition>
236-
<action>List detected technologies and ask for missing pieces</action>
237-
</scenario>
238-
</error_scenarios>
239-
240-
## Execution Summary
241-
242-
<final_checklist>
243-
<verify>
244-
- [ ] Codebase analyzed thoroughly
245-
- [ ] User context gathered
246-
- [ ] plan-product.md executed with proper context
247-
- [ ] Documentation customized for existing product
248-
- [ ] Team can adopt Agent OS workflow
249-
</verify>
250-
</final_checklist>
216+
<post_flight_check>
217+
EXECUTE: @.agent-os/instructions/meta/post-flight.md
218+
</post_flight_check>

0 commit comments

Comments
 (0)