Vous ne pouvez pas sélectionner plus de 25 sujets
Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
1.8KB
1.8KB
Workflow — Architecture Review
Purpose
Review design before major implementation.
Entry Criteria
- Product Owner has requested work.
- Relevant project context is available or assumptions are stated.
- Correct agents and skills are selected.
Steps
- Restate the goal.
- Identify the primary agent.
- Load needed skills.
- Define the expected output.
- Break work into small steps.
- Produce the result.
- Validate against the relevant checklist.
- Record important decisions.
- Propose file evolution when a durable lesson was learned.
Outputs
- Markdown summary
- Decisions
- Risks
- Tasks
- Test or validation notes
- Improvement proposals, when needed
Exit Criteria
- Product Owner can review or act.
- Work is traceable to a goal.
- Any unresolved issues are listed.
- No hidden assumptions remain.
Self-Evolution Protocol
This file is allowed to improve over time, but only through a controlled change process.
When to propose an update
An agent may propose an update when it learns:
- A recurring mistake should be prevented.
- A better workflow has been proven useful.
- A project-specific convention has become stable.
- A prompt pattern produced better results.
- A tool, framework, library, or deployment rule changed.
- The Product Owner approved a new standard.
How to update this file
Agents must not silently rewrite this file. They must create an improvement proposal using:
./.ai/evolution/improvement-proposal-template.md
Every proposal must include:
- File to update
- Current problem
- Proposed change
- Reason
- Risk
- Rollback plan
- Product Owner approval status
Learning Log
Add durable lessons here only after they are proven useful.
| Date | Lesson Learned | Change Made | Approved By |
|---|---|---|---|
| YYYY-MM-DD | Initial baseline created. | Created file. | Product Owner |