remove the current solution, add skills

2026-04-23 07:06:36 +00:00 · 2026-03-14 18:37:48 +02:00
parent fd75243a84
commit 767874cb90
363 changed files with 6057 additions and 36380 deletions
@@ -0,0 +1,108 @@
+# Feature Specification Template
+
+Create a focused behavioral specification that describes **what** the system should do, not **how** it should be built.
+Save as `TASKS_DIR/<topic>/[##]_[component_name]/[##].[##]_feature_[feature_name].md`.
+
+---
+
+```markdown
+# [Feature Name]
+
+**Status**: Draft | **Date**: [YYYY-MM-DD] | **Feature**: [Brief Feature Description]
+**Complexity**: [1|2|3|5] points
+**Dependencies**: [List dependent features or "None"]
+**Component**: [##]_[component_name]
+
+## 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 feature
+
+### 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 features
+
+## 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
+- Note dependencies on other features
+
+**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
@@ -0,0 +1,113 @@
+# Initial Structure Plan Template
+
+Use this template for the bootstrap structure plan. Save as `TASKS_DIR/<topic>/initial_structure.md`.
+
+---
+
+```markdown
+# Initial Project Structure Plan
+
+**Date**: [YYYY-MM-DD]
+**Tech Stack**: [language, framework, database, etc.]
+**Source**: architecture.md, component specs from _docs/02_plans/<topic>/
+
+## Project Folder Layout
+
+```
+project-root/
+├── [folder structure based on tech stack and components]
+└── ...
+```
+
+### Layout Rationale
+
+[Brief explanation of why this structure was chosen — language conventions, framework patterns, etc.]
+
+## DTOs and Interfaces
+
+### Shared DTOs
+
+| DTO Name | Used By Components | Fields Summary |
+|----------|-------------------|---------------|
+| [name] | [component list] | [key fields] |
+
+### Component Interfaces
+
+| Component | Interface | Methods | Exposed To |
+|-----------|-----------|---------|-----------|
+| [##]_[name] | [InterfaceName] | [method list] | [consumers] |
+
+## CI/CD Pipeline
+
+| Stage | Purpose | Trigger |
+|-------|---------|---------|
+| Build | Compile/bundle the application | Every push |
+| Lint / Static Analysis | Code quality and style checks | Every push |
+| Unit Tests | Run unit test suite | Every push |
+| Integration Tests | Run integration test suite | Every push |
+| Security Scan | SAST / dependency check | Every push |
+| Deploy to Staging | Deploy to staging environment | Merge to staging branch |
+
+### Pipeline Configuration Notes
+
+[Framework-specific notes: CI tool, runners, caching, parallelism, etc.]
+
+## Environment Strategy
+
+| Environment | Purpose | Configuration Notes |
+|-------------|---------|-------------------|
+| Development | Local development | [local DB, mock services, debug flags] |
+| Staging | Pre-production testing | [staging DB, staging services, production-like config] |
+| Production | Live system | [production DB, real services, optimized config] |
+
+### Environment Variables
+
+| Variable | Dev | Staging | Production | Description |
+|----------|-----|---------|------------|-------------|
+| [VAR_NAME] | [value/source] | [value/source] | [value/source] | [purpose] |
+
+## Database Migration Approach
+
+**Migration tool**: [tool name]
+**Strategy**: [migration strategy — e.g., versioned scripts, ORM migrations]
+
+### Initial Schema
+
+[Key tables/collections that need to be created, referencing component data access patterns]
+
+## Test Structure
+
+```
+tests/
+├── unit/
+│   ├── [component_1]/
+│   ├── [component_2]/
+│   └── ...
+├── integration/
+│   ├── test_data/
+│   └── [test files]
+└── ...
+```
+
+### Test Configuration Notes
+
+[Test runner, fixtures, test data management, isolation strategy]
+
+## Implementation Order
+
+| Order | Component | Reason |
+|-------|-----------|--------|
+| 1 | [##]_[name] | [why first — foundational, no dependencies] |
+| 2 | [##]_[name] | [depends on #1] |
+| ... | ... | ... |
+```
+
+---
+
+## Guidance Notes
+
+- This is a PLAN document, not code. The `3.05_implement_initial_structure` command executes it.
+- Focus on structure and organization decisions, not implementation details.
+- Reference component specs for interface and DTO details — don't repeat everything.
+- The folder layout should follow conventions of the identified tech stack.
+- Environment strategy should account for secrets management and configuration.
@@ -0,0 +1,59 @@
+# Decomposition Summary Template
+
+Use this template after all steps complete. Save as `TASKS_DIR/<topic>/SUMMARY.md`.
+
+---
+
+```markdown
+# Decomposition Summary
+
+**Date**: [YYYY-MM-DD]
+**Topic**: [topic name]
+**Total Components**: [N]
+**Total Features**: [N]
+**Total Complexity Points**: [N]
+
+## Component Breakdown
+
+| # | Component | Features | Total Points | Jira Epic |
+|---|-----------|----------|-------------|-----------|
+| 01 | [name] | [count] | [sum] | [EPIC-ID] |
+| 02 | [name] | [count] | [sum] | [EPIC-ID] |
+| ... | ... | ... | ... | ... |
+
+## Feature List
+
+| Component | Feature | Complexity | Jira Task | Dependencies |
+|-----------|---------|-----------|-----------|-------------|
+| [##]_[name] | [##].[##]_feature_[name] | [points] | [TASK-ID] | [deps or "None"] |
+| ... | ... | ... | ... | ... |
+
+## Implementation Order
+
+Recommended sequence based on dependency analysis:
+
+| Phase | Components / Features | Rationale |
+|-------|----------------------|-----------|
+| 1 | [list] | [foundational, no dependencies] |
+| 2 | [list] | [depends on phase 1] |
+| 3 | [list] | [depends on phase 1-2] |
+| ... | ... | ... |
+
+### Parallelization Opportunities
+
+[Features/components that can be implemented concurrently within each phase]
+
+## Cross-Component Dependencies
+
+| From (Feature) | To (Feature) | Dependency Type |
+|----------------|-------------|-----------------|
+| [comp.feature] | [comp.feature] | [data / API / event] |
+| ... | ... | ... |
+
+## Artifacts Produced
+
+- `initial_structure.md` — project skeleton plan
+- `cross_dependencies.md` — dependency matrix
+- `[##]_[name]/[##].[##]_feature_*.md` — feature specs per component
+- Jira tasks created under respective epics
+```