Update TechStackAgent documentation to reflect new template location …#8
Merged
Update TechStackAgent documentation to reflect new template location …#8
Conversation
…and remove obsolete tech stack template file. The changes ensure clarity in documentation sources and streamline the tech stack documentation process.
…ecution. Key updates include redefining the primary goal to emphasize concrete implementation tasks, refining workflow steps to prioritize execution-focused outputs, and clarifying boundaries to exclude process tasks. This ensures that developers can implement plans with minimal clarification and that validation is embedded within tasks.
…w directory structure. Key updates include: - Updated resource strategy to reflect changes in task storage paths, emphasizing the use of `workspace/` for project-specific artifacts. - Revised output packaging instructions to ensure task prompt files are created directly in the new structure. - Clarified validation and communication expectations for task outputs. These changes enhance clarity and usability for developers implementing task prompts within the updated DevAgent framework.
Relocate all 12 agent markdown files from .devagent/agents/ to .devagent/core/agents/ to establish the portable agent kit. This includes preserving the codegen/ subdirectory structure for CodegenBackgroundAgent.md. Part of core/workspace split to enable 'copy this folder' DevAgent adoption pattern. Co-authored-by: Jake Ruesink <jaruesink@gmail.com>
Relocate all 9 template markdown files from .devagent/templates/ to .devagent/core/templates/ to establish the reusable template library. These templates provide standardized formats for agent outputs and project artifacts. Part of core/workspace split to enable portable DevAgent kit distribution. Co-authored-by: Jake Ruesink <jaruesink@gmail.com>
Relocate the feature hub template from .devagent/features/_template/ to .devagent/core/templates/feature-hub-template/ to position it as a reusable scaffold in the portable agent kit. The feature hub template provides the standard structure for organizing feature development work including research and spec subdirectories. Part of core/workspace split to enable easy feature hub creation across projects. Co-authored-by: Jake Ruesink <jaruesink@gmail.com>
Relocate project-specific working files from flat .devagent/ directories into .devagent/workspace/ subdirectories: - product/ → workspace/product/ (mission.md, roadmap.md, guiding-questions.md) - memory/ → workspace/memory/ (constitution.md, decision-journal.md, tech-stack.md, overview.md) - features/README.md → workspace/features/README.md - research/ → workspace/research/ (research markdown files) This separates project-specific artifacts from the portable agent kit, enabling clean cross-project DevAgent adoption by copying only the core/ directory. Part of core/workspace split to establish clear 'copy vs customize' boundaries. Co-authored-by: Jake Ruesink <jaruesink@gmail.com>
…dated directory structure. Key changes include: - Adjusted resource strategy to utilize `workspace/` for project-specific artifacts. - Updated output packaging instructions for task prompt files to fit the new structure. - Enhanced clarity on validation and communication expectations for task outputs. These updates aim to streamline the task prompt creation process and enhance usability for developers within the DevAgent framework.
…y/devagent into feature/core-workspace-split
…es as part of the core/workspace split. This cleanup eliminates obsolete documentation and tasks related to the execution directive, streamlining the DevAgent framework for improved usability and clarity in project setup.
- Updated all agent instruction files to use new path conventions - Template paths: .devagent/agents/ → .devagent/core/agents/ - Template paths: .devagent/templates/ → .devagent/core/templates/ - Working paths: .devagent/product/ → .devagent/workspace/product/ - Working paths: .devagent/memory/ → .devagent/workspace/memory/ - Working paths: .devagent/features/ → .devagent/workspace/features/ - Working paths: .devagent/research/ → .devagent/workspace/research/ Files updated (11): - AgentBuilder.md - FeatureBrainstormAgent.md - FeatureClarifyAgent.md - ProductMissionPartner.md - ResearchAgent.md - SpecArchitect.md - TaskExecutor.md - TaskPlanner.md - TechStackAgent.md - UpdateConstitution.md - codegen/CodegenBackgroundAgent.md Validation: grep confirmed no old path patterns remain in agent files Co-authored-by: Jake Ruesink <jaruesink@gmail.com>
- Update AGENTS.md: All 10 agent references now use .devagent/core/agents/ paths - Create core/README.md: Comprehensive setup guide with directory structure and 5-minute setup instructions - Create core/AGENTS.md: Portable copy of agent roster for kit completeness - Update root README.md: Add structure section explaining core vs workspace, update all path references - Update templates: All self-references now use workspace/ paths for outputs This completes the documentation layer for the core-workspace split, enabling teams to easily adopt DevAgent in new projects by copying the portable core/ kit. Co-authored-by: Jake Ruesink <jaruesink@gmail.com>
|
Caution Review failedThe pull request is closed. WalkthroughReorganizes DevAgent into core (portable) and workspace (project) directories, updates all agent/docs/templates to new paths, removes the old TaskPlanner and adds a new TaskPlanner doc under core, and adds feature hubs for “Core-Workspace Split” and “Agent Execution Directive,” plus updated top-level and core AGENTS/README docs. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
✨ Finishing touches🧪 Generate unit tests
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (31)
Comment |
This was referenced Oct 7, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…and remove obsolete tech stack template file. The changes ensure clarity in documentation sources and streamline the tech stack documentation process.
Summary by CodeRabbit
New Features
Documentation
Refactor
Chores