mirror of
https://github.com/sstent/FitTrack_ReportGenerator.git
synced 2025-12-06 08:01:40 +00:00
sstent
9e0bd322d3
This commit introduces the initial version of the FitTrack Report Generator, a FastAPI application for analyzing workout files. Key features include: - Parsing of FIT, TCX, and GPX workout files. - Analysis of power, heart rate, speed, and elevation data. - Generation of summary reports and charts. - REST API for single and batch workout analysis. The project structure has been set up with a `src` directory for core logic, an `api` directory for the FastAPI application, and a `tests` directory for unit, integration, and contract tests. The development workflow is configured to use Docker and modern Python tooling.
94 lines
4.5 KiB
TOML
94 lines
4.5 KiB
TOML
description = "Execute the implementation plan by processing and executing all tasks defined in tasks.md"
|
|
|
|
prompt = """
|
|
---
|
|
description: Execute the implementation plan by processing and executing all tasks defined in tasks.md
|
|
---
|
|
|
|
## User Input
|
|
|
|
```text
|
|
$ARGUMENTS
|
|
```
|
|
|
|
You **MUST** consider the user input before proceeding (if not empty).
|
|
|
|
## Outline
|
|
|
|
1. Run `.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute.
|
|
|
|
2. **Check checklists status** (if FEATURE_DIR/checklists/ exists):
|
|
- Scan all checklist files in the checklists/ directory
|
|
- For each checklist, count:
|
|
* Total items: All lines matching `- [ ]` or `- [X]` or `- [x]`
|
|
* Completed items: Lines matching `- [X]` or `- [x]`
|
|
* Incomplete items: Lines matching `- [ ]`
|
|
- Create a status table:
|
|
```
|
|
| Checklist | Total | Completed | Incomplete | Status |
|
|
|-----------|-------|-----------|------------|--------|
|
|
| ux.md | 12 | 12 | 0 | ✓ PASS |
|
|
| test.md | 8 | 5 | 3 | ✗ FAIL |
|
|
| security.md | 6 | 6 | 0 | ✓ PASS |
|
|
```
|
|
- Calculate overall status:
|
|
* **PASS**: All checklists have 0 incomplete items
|
|
* **FAIL**: One or more checklists have incomplete items
|
|
|
|
- **If any checklist is incomplete**:
|
|
* Display the table with incomplete item counts
|
|
* **STOP** and ask: "Some checklists are incomplete. Do you want to proceed with implementation anyway? (yes/no)"
|
|
* Wait for user response before continuing
|
|
* If user says "no" or "wait" or "stop", halt execution
|
|
* If user says "yes" or "proceed" or "continue", proceed to step 3
|
|
|
|
- **If all checklists are complete**:
|
|
* Display the table showing all checklists passed
|
|
* Automatically proceed to step 3
|
|
|
|
3. Load and analyze the implementation context:
|
|
- **REQUIRED**: Read tasks.md for the complete task list and execution plan
|
|
- **REQUIRED**: Read plan.md for tech stack, architecture, and file structure
|
|
- **IF EXISTS**: Read data-model.md for entities and relationships
|
|
- **IF EXISTS**: Read contracts/ for API specifications and test requirements
|
|
- **IF EXISTS**: Read research.md for technical decisions and constraints
|
|
- **IF EXISTS**: Read quickstart.md for integration scenarios
|
|
|
|
4. Parse tasks.md structure and extract:
|
|
- **Task phases**: Setup, Tests, Core, Integration, Polish
|
|
- **Task dependencies**: Sequential vs parallel execution rules
|
|
- **Task details**: ID, description, file paths, parallel markers [P]
|
|
- **Execution flow**: Order and dependency requirements
|
|
|
|
5. Execute implementation following the task plan:
|
|
- **Phase-by-phase execution**: Complete each phase before moving to the next
|
|
- **Respect dependencies**: Run sequential tasks in order, parallel tasks [P] can run together
|
|
- **Follow TDD approach**: Execute test tasks before their corresponding implementation tasks
|
|
- **File-based coordination**: Tasks affecting the same files must run sequentially
|
|
- **Validation checkpoints**: Verify each phase completion before proceeding
|
|
|
|
6. Implementation execution rules:
|
|
- **Setup first**: Initialize project structure, dependencies, configuration
|
|
- **Tests before code**: If you need to write tests for contracts, entities, and integration scenarios
|
|
- **Core development**: Implement models, services, CLI commands, endpoints
|
|
- **Integration work**: Database connections, middleware, logging, external services
|
|
- **Polish and validation**: Unit tests, performance optimization, documentation
|
|
|
|
7. Progress tracking and error handling:
|
|
- Report progress after each completed task
|
|
- Halt execution if any non-parallel task fails
|
|
- For parallel tasks [P], continue with successful tasks, report failed ones
|
|
- Provide clear error messages with context for debugging
|
|
- Suggest next steps if implementation cannot proceed
|
|
- **IMPORTANT** For completed tasks, make sure to mark the task off as [X] in the tasks file.
|
|
|
|
8. Completion validation:
|
|
- Verify all required tasks are completed
|
|
- Check that implemented features match the original specification
|
|
- Validate that tests pass and coverage meets requirements
|
|
- Confirm the implementation follows the technical plan
|
|
- Report final status with summary of completed work
|
|
|
|
Note: This command assumes a complete task breakdown exists in tasks.md. If tasks are incomplete or missing, suggest running `/tasks` first to regenerate the task list.
|
|
"""
|