Archive all completed changes and create final specifications: Archived changes (2025-11-03): - add-application-email (8 requirements) - add-application-management (9 requirements) - add-application-validation (9 requirements) - add-cover-letter-generation (13 requirements) - add-cover-letter-pdf-conversion (7 requirements) - add-profile-template (4 requirements) - add-profile-validation (3 requirements) Created specifications: - applicant-profile: User profile management with validation - application-email: Email generation for job applications - application-management: Application workflow and folder structure - application-validation: Application completeness checking - cover-letter-generation: Tailored cover letter creation - cover-letter-pdf-conversion: PDF export with Swiss formatting All features are now fully documented in openspec/specs/ and ready for use. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
59 lines
2.6 KiB
Markdown
59 lines
2.6 KiB
Markdown
# Implementation Tasks
|
|
|
|
## 1. Update Application Folder Structure
|
|
|
|
- [ ] 1.1 Modify `src/.claude/commands/new-application.md` to create `attachments/` subfolder
|
|
- [ ] 1.2 Add creation of `.keep` file inside `attachments/` folder for version control
|
|
- [ ] 1.3 Update success message in new-application to mention attachments folder
|
|
- [ ] 1.4 Update test framework at `~/workspace/test-bewerbungen/` with new application structure
|
|
|
|
## 2. Create Email Generation Command
|
|
|
|
- [ ] 2.1 Create `src/.claude/commands/write-application-email.md` command file
|
|
- [ ] 2.2 Implement command argument parsing (application name, flags: --force, --help)
|
|
- [ ] 2.3 Implement location detection (current directory or parameter-based)
|
|
- [ ] 2.4 Add document verification logic (check for CV, cover letter, certificates in attachments/)
|
|
- [ ] 2.5 Implement email subject line generation based on job title and company
|
|
- [ ] 2.6 Implement email body generation with document references
|
|
- [ ] 2.7 Add language detection (German/English) similar to cover letter
|
|
- [ ] 2.8 Add tone adaptation (Formal/Balanced/Casual) from application.md
|
|
- [ ] 2.9 Implement file existence checks and user-friendly error messages
|
|
- [ ] 2.10 Write generated email to `application-email.md` in application folder
|
|
|
|
## 3. Testing & Quality Assurance
|
|
|
|
- [ ] 3.1 Test new-application creates attachments folder correctly
|
|
- [ ] 3.2 Test write-application-email with all required documents present
|
|
- [ ] 3.3 Test write-application-email with missing documents (error handling)
|
|
- [ ] 3.4 Test --force flag to overwrite existing email
|
|
- [ ] 3.5 Test language detection (German/English)
|
|
- [ ] 3.6 Test tone variations (Formal/Balanced/Casual)
|
|
- [ ] 3.7 Verify error messages are clear and actionable
|
|
|
|
## 4. Documentation
|
|
|
|
- [ ] 4.1 Update main CLAUDE.md with write-application-email command reference
|
|
- [ ] 4.2 Add email generation step to workflow documentation
|
|
- [ ] 4.3 Update example usage sections with email generation examples
|
|
- [ ] 4.4 Document attachments folder structure and purpose
|
|
|
|
## 5. Integration
|
|
|
|
- [ ] 5.1 Ensure email command integrates with existing validation workflow
|
|
- [ ] 5.2 Verify consistency with write-cover-letter command pattern
|
|
- [ ] 5.3 Test end-to-end workflow: new-application → populate → validate → cover-letter → email
|
|
|
|
## Dependencies
|
|
|
|
- Tasks 2.x depend on 1.x (attachments folder must exist)
|
|
- Tasks 3.x depend on 1.x and 2.x (implementation must be complete)
|
|
- Tasks 5.x depend on all previous tasks
|
|
|
|
## Verification Criteria
|
|
|
|
Each task is considered complete when:
|
|
- Code is written and tested
|
|
- Error cases are handled gracefully
|
|
- User-facing messages are clear and helpful
|
|
- Functionality matches specification
|