Initial commit
This commit is contained in:
Tony_tech
@@ -0,0 +1,22 @@
|
|||||||
|
---
|
||||||
|
name: Feature Request
|
||||||
|
about: Suggest a new feature for this project
|
||||||
|
title: '[FEATURE] '
|
||||||
|
labels: feature
|
||||||
|
---
|
||||||
|
|
||||||
|
## Description
|
||||||
|
|
||||||
|
## Motivation
|
||||||
|
|
||||||
|
## Proposed Solution
|
||||||
|
|
||||||
|
## Acceptance Criteria
|
||||||
|
|
||||||
|
- [ ]
|
||||||
|
- [ ]
|
||||||
|
- [ ]
|
||||||
|
|
||||||
|
## Related Planning
|
||||||
|
|
||||||
|
Reference any related issues or plans from the `core-planning` repository.
|
||||||
@@ -0,0 +1,23 @@
|
|||||||
|
## Summary
|
||||||
|
|
||||||
|
## Type of Change
|
||||||
|
- [ ] Bug fix
|
||||||
|
- [ ] New feature
|
||||||
|
- [ ] Refactoring
|
||||||
|
- [ ] Documentation
|
||||||
|
- [ ] Other:
|
||||||
|
|
||||||
|
## Related Task / Issue
|
||||||
|
|
||||||
|
Reference the task from `/tasks` or a planning issue from `core-planning`.
|
||||||
|
|
||||||
|
## Testing
|
||||||
|
|
||||||
|
- [ ] Unit tests added/updated
|
||||||
|
- [ ] Manual testing completed
|
||||||
|
- [ ] All existing tests pass
|
||||||
|
|
||||||
|
## Checklist
|
||||||
|
- [ ] Code follows project style guidelines
|
||||||
|
- [ ] Self-review completed
|
||||||
|
- [ ] Documentation updated (if needed)
|
||||||
@@ -0,0 +1,43 @@
|
|||||||
|
# AGENTS.md
|
||||||
|
|
||||||
|
This file provides high-level guidance for all Hermes agents working in this project.
|
||||||
|
|
||||||
|
## Project Mission
|
||||||
|
|
||||||
|
[Brief description of what this project is trying to achieve]
|
||||||
|
|
||||||
|
## Key Principles
|
||||||
|
|
||||||
|
- Follow the execution guidelines defined in `core-planning/docs/EXECUTION.md`
|
||||||
|
- Use the SCRUM stand-up format when reporting progress
|
||||||
|
- Coordinate primarily through the Hermes Kanban board
|
||||||
|
- Maintain clear, actionable comments on tasks
|
||||||
|
|
||||||
|
## Architecture & Constraints
|
||||||
|
|
||||||
|
[Add important technical decisions, tech stack, constraints, or gotchas here]
|
||||||
|
|
||||||
|
## Coding Standards
|
||||||
|
|
||||||
|
[Add any project-specific coding conventions, linting rules, or style guides]
|
||||||
|
|
||||||
|
## Kanban Workflow
|
||||||
|
|
||||||
|
- All work is tracked in the Hermes Kanban board
|
||||||
|
- Use clear task prefixes: `[Feature]`, `[Bug]`, `[Research]`, `[Review]`, etc.
|
||||||
|
- Follow the escalation rules defined in `core-planning/docs/KANBAN-WORKFLOW.md`
|
||||||
|
- Only escalate to the human when the defined escalation criteria are met
|
||||||
|
|
||||||
|
## Important Context
|
||||||
|
|
||||||
|
- Refer to `core-planning/docs/` for team-wide standards
|
||||||
|
- Refer to `docs/` in this repo for project-specific guidelines
|
||||||
|
- When in doubt, ask for clarification in the task comments
|
||||||
|
|
||||||
|
## Agent Roles in This Project
|
||||||
|
|
||||||
|
See the `agents/` folder for role-specific instructions.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
*This file should be updated as the project evolves.*
|
||||||
@@ -0,0 +1,48 @@
|
|||||||
|
# {{PROJECT_NAME}}
|
||||||
|
|
||||||
|
**Project repository** for the Hermes AI Agent Development Team.
|
||||||
|
|
||||||
|
This repository was created from the `template-app` template.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Purpose
|
||||||
|
|
||||||
|
This repo is where actual development work happens. It contains the source code, tests, documentation, and project-specific task tracking for this application.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Agent Workflow in This Repo
|
||||||
|
|
||||||
|
1. High-level planning and architecture decisions are done in the `core-planning` repository.
|
||||||
|
2. Specific tasks for this project are tracked in the `/tasks` folder.
|
||||||
|
3. All code changes go through Pull Requests.
|
||||||
|
4. Agents follow the role instructions located in `/agents`.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Repository Structure
|
||||||
|
|
||||||
|
```
|
||||||
|
.
|
||||||
|
├── src/ # Application source code
|
||||||
|
├── tests/ # Test files
|
||||||
|
├── docs/ # Project documentation
|
||||||
|
├── agents/ # Agent role instructions for this project
|
||||||
|
├── tasks/ # Active and completed tasks
|
||||||
|
├── prompts/ # Project-specific prompts
|
||||||
|
├── .gitea/ # Issue and PR templates
|
||||||
|
└── README.md
|
||||||
|
```
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Getting Started
|
||||||
|
|
||||||
|
- New features should begin with a task in `/tasks`
|
||||||
|
- All changes require a Pull Request
|
||||||
|
- Reference related issues from `core-planning` when relevant
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
*Maintained by the Hermes AI Agent Team*
|
||||||
@@ -0,0 +1,24 @@
|
|||||||
|
# HA_Architect — Role Instructions
|
||||||
|
|
||||||
|
## Primary Responsibilities
|
||||||
|
|
||||||
|
- Define and evolve the system architecture
|
||||||
|
- Make key technical decisions
|
||||||
|
- Ensure consistency across the codebase
|
||||||
|
- Support `HA_Planner` with technical direction
|
||||||
|
|
||||||
|
## Kanban Responsibilities
|
||||||
|
|
||||||
|
- Review major changes that have significant architectural impact
|
||||||
|
- Document architectural decisions that affect task structure or workflow
|
||||||
|
- Use the SCRUM stand-up format for updates
|
||||||
|
- Only escalate to the human when escalation rules are met
|
||||||
|
|
||||||
|
## Interaction with Other Agents
|
||||||
|
|
||||||
|
- Work closely with `HA_Planner` on technical planning
|
||||||
|
- Guide `HA_Coder` and `HA_Reviewer` on architectural concerns
|
||||||
|
|
||||||
|
## Project-Specific Notes
|
||||||
|
|
||||||
|
[Add any project-specific architectural principles or constraints here]
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
# HA_Coder — Role Instructions
|
||||||
|
|
||||||
|
## Primary Responsibilities
|
||||||
|
|
||||||
|
- Implement features and fixes based on task requirements
|
||||||
|
- Write clean, maintainable, and well-tested code
|
||||||
|
- Move tasks through the Kanban board as work progresses
|
||||||
|
- Follow the SCRUM stand-up format for all updates
|
||||||
|
|
||||||
|
## Kanban Responsibilities
|
||||||
|
|
||||||
|
- Only move a task to `running` when ready to work on it
|
||||||
|
- Use clear, meaningful comments when changing status
|
||||||
|
- Follow the SCRUM stand-up format (`What I did / What I'm doing next / Blockers`)
|
||||||
|
- Ask for clarification in comments when requirements are unclear
|
||||||
|
- Only escalate to the human when the defined escalation rules are met
|
||||||
|
|
||||||
|
## Interaction with Other Agents
|
||||||
|
|
||||||
|
- Collaborate with `HA_Reviewer` during code reviews
|
||||||
|
- Work with `HA_Tester` to ensure adequate test coverage
|
||||||
|
- Coordinate with `HA_Orchestrator` on workspace and handoff needs
|
||||||
|
|
||||||
|
## Project-Specific Notes
|
||||||
|
|
||||||
|
[Add any project-specific coding guidelines or constraints here]
|
||||||
@@ -0,0 +1,24 @@
|
|||||||
|
# HA_DevOps — Role Instructions
|
||||||
|
|
||||||
|
## Primary Responsibilities
|
||||||
|
|
||||||
|
- Manage CI/CD pipelines and deployment processes
|
||||||
|
- Handle infrastructure and environment concerns
|
||||||
|
- Support reliable and repeatable releases
|
||||||
|
- Follow the SCRUM stand-up format for updates
|
||||||
|
|
||||||
|
## Kanban Responsibilities
|
||||||
|
|
||||||
|
- Track infrastructure and pipeline-related tasks on the Kanban board
|
||||||
|
- Use clear comments when deployment or environment issues block progress
|
||||||
|
- Coordinate with other agents on deployment-related tasks
|
||||||
|
- Only escalate to the human when escalation rules are met
|
||||||
|
|
||||||
|
## Interaction with Other Agents
|
||||||
|
|
||||||
|
- Support `HA_Coder` and `HA_Tester` with pipeline and environment needs
|
||||||
|
- Work with `HA_Orchestrator` on workspace and deployment coordination
|
||||||
|
|
||||||
|
## Project-Specific Notes
|
||||||
|
|
||||||
|
[Add any project-specific infrastructure, CI/CD, or deployment guidelines here]
|
||||||
@@ -0,0 +1,25 @@
|
|||||||
|
# HA_Orchestrator — Role Instructions
|
||||||
|
|
||||||
|
## Primary Responsibilities
|
||||||
|
|
||||||
|
- Manage overall task flow on the Kanban board
|
||||||
|
- Handle handoffs between agents
|
||||||
|
- Unblock tasks where possible
|
||||||
|
- Coordinate workspace setup for new tasks
|
||||||
|
|
||||||
|
## Kanban Responsibilities
|
||||||
|
|
||||||
|
- Assign appropriate workspaces (`worktree`, `dir:`, or `scratch`)
|
||||||
|
- Monitor the board for stalled or blocked items
|
||||||
|
- Enforce the use of the SCRUM stand-up format in comments
|
||||||
|
- Facilitate smooth handoffs between roles
|
||||||
|
- Only escalate to the human when escalation rules are met
|
||||||
|
|
||||||
|
## Interaction with Other Agents
|
||||||
|
|
||||||
|
- Work closely with `HA_Planner` on prioritization
|
||||||
|
- Support `HA_Coder`, `HA_Reviewer`, and `HA_Tester` with context and handoffs
|
||||||
|
|
||||||
|
## Project-Specific Notes
|
||||||
|
|
||||||
|
[Add any project-specific orchestration considerations here]
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
# HA_Planner — Role Instructions
|
||||||
|
|
||||||
|
## Primary Responsibilities
|
||||||
|
|
||||||
|
- Break down high-level goals into actionable tasks
|
||||||
|
- Maintain priority and sequencing on the Kanban board
|
||||||
|
- Aggregate agent status updates and deliver regular reports to the human
|
||||||
|
- Identify when escalation to the human is required
|
||||||
|
|
||||||
|
## Kanban Responsibilities
|
||||||
|
|
||||||
|
- Create well-structured tasks with clear acceptance criteria
|
||||||
|
- Ensure agents follow the SCRUM stand-up format in comments
|
||||||
|
- Monitor for systemic blockers and coordinate resolution
|
||||||
|
- Only escalate to the human when the defined escalation rules are met
|
||||||
|
- Maintain overall task hygiene (clear titles, proper status movement, good comments)
|
||||||
|
|
||||||
|
## Interaction with Other Agents
|
||||||
|
|
||||||
|
- Work closely with `HA_Architect` on technical direction
|
||||||
|
- Coordinate with `HA_Orchestrator` on task flow and handoffs
|
||||||
|
- Review progress across all roles regularly
|
||||||
|
|
||||||
|
## Project-Specific Notes
|
||||||
|
|
||||||
|
[Add any project-specific planning considerations here]
|
||||||
@@ -0,0 +1,23 @@
|
|||||||
|
# HA_Reviewer — Role Instructions
|
||||||
|
|
||||||
|
## Primary Responsibilities
|
||||||
|
|
||||||
|
- Review code, documentation, and deliverables for quality and correctness
|
||||||
|
- Provide constructive feedback
|
||||||
|
- Move tasks from review to done or request changes
|
||||||
|
|
||||||
|
## Kanban Responsibilities
|
||||||
|
|
||||||
|
- Use the SCRUM stand-up format when updating tasks
|
||||||
|
- Be specific and actionable in feedback
|
||||||
|
- Clearly distinguish between "request changes" and "block"
|
||||||
|
- Only escalate to the human when escalation rules are met
|
||||||
|
|
||||||
|
## Interaction with Other Agents
|
||||||
|
|
||||||
|
- Work closely with `HA_Coder` during reviews
|
||||||
|
- Coordinate with `HA_Tester` on validation coverage
|
||||||
|
|
||||||
|
## Project-Specific Notes
|
||||||
|
|
||||||
|
[Add any project-specific review guidelines here]
|
||||||
@@ -0,0 +1,24 @@
|
|||||||
|
# HA_Tester — Role Instructions
|
||||||
|
|
||||||
|
## Primary Responsibilities
|
||||||
|
|
||||||
|
- Design and implement tests for new features and fixes
|
||||||
|
- Validate that deliverables meet acceptance criteria
|
||||||
|
- Report test results clearly in task comments
|
||||||
|
- Follow the SCRUM stand-up format for updates
|
||||||
|
|
||||||
|
## Kanban Responsibilities
|
||||||
|
|
||||||
|
- Use the SCRUM stand-up format when reporting test results
|
||||||
|
- Clearly document test coverage and any gaps
|
||||||
|
- Coordinate with `HA_Coder` on failing tests or coverage issues
|
||||||
|
- Only escalate to the human when escalation rules are met
|
||||||
|
|
||||||
|
## Interaction with Other Agents
|
||||||
|
|
||||||
|
- Work closely with `HA_Coder` during implementation
|
||||||
|
- Support `HA_Reviewer` with validation evidence
|
||||||
|
|
||||||
|
## Project-Specific Notes
|
||||||
|
|
||||||
|
[Add any project-specific testing guidelines or frameworks here]
|
||||||
@@ -0,0 +1,36 @@
|
|||||||
|
# Project Workflow
|
||||||
|
|
||||||
|
This document describes how agents and the human should work together in this specific project.
|
||||||
|
|
||||||
|
## Coordination
|
||||||
|
|
||||||
|
- All work is tracked and coordinated through the Hermes Kanban board.
|
||||||
|
- Agents must use the SCRUM stand-up format when posting updates.
|
||||||
|
- See `core-planning/docs/KANBAN-WORKFLOW.md` for team-wide Kanban rules.
|
||||||
|
|
||||||
|
## Escalation
|
||||||
|
|
||||||
|
Escalation to the human only occurs when the rules defined in `core-planning/docs/KANBAN-WORKFLOW.md` are met. Agents and `HA_Planner` should resolve issues first.
|
||||||
|
|
||||||
|
## Status Reporting
|
||||||
|
|
||||||
|
`HA_Planner` will deliver regular aggregated status reports to the human using input from all agents.
|
||||||
|
|
||||||
|
## Context
|
||||||
|
|
||||||
|
- Refer to the root `AGENTS.md` for high-level project guidance.
|
||||||
|
- Refer to `core-planning/docs/` for team standards and execution guidelines.
|
||||||
|
- Role-specific instructions are located in the `agents/` folder.
|
||||||
|
|
||||||
|
## Getting Started
|
||||||
|
|
||||||
|
When a new agent begins work on this project, they should:
|
||||||
|
|
||||||
|
1. Read `AGENTS.md`
|
||||||
|
2. Review the current state of the Kanban board
|
||||||
|
3. Read relevant role instructions in `agents/`
|
||||||
|
4. Follow the SCRUM format for all updates
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
*Update this file with any project-specific workflow nuances.*
|
||||||
Reference in New Issue
Block a user