Update README and implementer documentation to reflect changes in task orchestration and structure. Remove obsolete commands and templates related to initial implementation and code review. Enhance task decomposition workflow and clarify input specifications for improved task management.

2026-04-23 02:46:36 +00:00 · 2026-03-18 18:41:22 +02:00
parent d969bec3b6
commit ae69d02f1e
15 changed files with 659 additions and 400 deletions
@@ -0,0 +1,113 @@
+# Task Specification Template
+
+Create a focused behavioral specification that describes **what** the system should do, not **how** it should be built.
+Save as `TASKS_DIR/[##]_[short_name].md` initially, then rename to `TASKS_DIR/[JIRA-ID]_[short_name].md` after Jira ticket creation.
+
+---
+
+```markdown
+# [Feature Name]
+
+**Task**: [JIRA-ID]_[short_name]
+**Name**: [short human name]
+**Description**: [one-line description of what this task delivers]
+**Complexity**: [1|2|3|5] points
+**Dependencies**: [AZ-43_shared_models, AZ-44_db_migrations] or "None"
+**Component**: [component name for context]
+**Jira**: [TASK-ID]
+**Epic**: [EPIC-ID]
+
+## Problem
+
+Clear, concise statement of the problem users are facing.
+
+## Outcome
+
+- Measurable or observable goal 1
+- Measurable or observable goal 2
+- ...
+
+## Scope
+
+### Included
+- What's in scope for this task
+
+### Excluded
+- Explicitly what's NOT in scope
+
+## Acceptance Criteria
+
+**AC-1: [Title]**
+Given [precondition]
+When [action]
+Then [expected result]
+
+**AC-2: [Title]**
+Given [precondition]
+When [action]
+Then [expected result]
+
+## Non-Functional Requirements
+
+**Performance**
+- [requirement if relevant]
+
+**Compatibility**
+- [requirement if relevant]
+
+**Reliability**
+- [requirement if relevant]
+
+## Unit Tests
+
+| AC Ref | What to Test | Required Outcome |
+|--------|-------------|-----------------|
+| AC-1 | [test subject] | [expected result] |
+
+## Integration Tests
+
+| AC Ref | Initial Data/Conditions | What to Test | Expected Behavior | NFR References |
+|--------|------------------------|-------------|-------------------|----------------|
+| AC-1 | [setup] | [test subject] | [expected behavior] | [NFR if any] |
+
+## Constraints
+
+- [Architectural pattern constraint if critical]
+- [Technical limitation]
+- [Integration requirement]
+
+## Risks & Mitigation
+
+**Risk 1: [Title]**
+- *Risk*: [Description]
+- *Mitigation*: [Approach]
+```
+
+---
+
+## Complexity Points Guide
+
+- 1 point: Trivial, self-contained, no dependencies
+- 2 points: Non-trivial, low complexity, minimal coordination
+- 3 points: Multi-step, moderate complexity, potential alignment needed
+- 5 points: Difficult, interconnected logic, medium-high risk
+- 8 points: Too complex — split into smaller tasks
+
+## Output Guidelines
+
+**DO:**
+- Focus on behavior and user experience
+- Use clear, simple language
+- Keep acceptance criteria testable (Gherkin format)
+- Include realistic scope boundaries
+- Write from the user's perspective
+- Include complexity estimation
+- Reference dependencies by Jira ID (e.g., AZ-43_shared_models)
+
+**DON'T:**
+- Include implementation details (file paths, classes, methods)
+- Prescribe technical solutions or libraries
+- Add architectural diagrams or code examples
+- Specify exact API endpoints or data structures
+- Include step-by-step implementation instructions
+- Add "how to build" guidance