gurixandClaude
a4d390aa03
Add OpenSpec proposal for /write-application-email command that: - Generates professional application emails with subject lines - Verifies documents exist in attachments/ folder before generation - Updates /new-application to create attachments/ subfolder - Follows similar pattern to /write-cover-letter command Specs: - application-email: 9 requirements for email generation - application-management: 3 requirements for folder structure OpenSpec: add-application-email 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
64 lines
2.6 KiB
Markdown
64 lines
2.6 KiB
Markdown
# Application Management Specification
|
|
|
|
## ADDED Requirements
|
|
|
|
### Requirement: Attachments Folder Creation
|
|
|
|
The system SHALL create an `attachments/` subfolder with a `.keep` file when initializing new applications to support document organization for email generation.
|
|
|
|
#### Scenario: Application folder creation includes attachments directory
|
|
|
|
- **WHEN** user runs `/new-application "Company - Job Title"`
|
|
- **THEN** the system creates folder structure: `applications/pending/[folder-name]/attachments/`
|
|
- **AND** creates an empty `.keep` file inside `attachments/` folder
|
|
- **AND** the attachments folder is ready for user to add documents
|
|
|
|
#### Scenario: Version control compatibility
|
|
|
|
- **WHEN** attachments folder is created with `.keep` file
|
|
- **THEN** the empty folder can be tracked in version control systems
|
|
- **AND** the folder structure is preserved even when empty
|
|
|
|
#### Scenario: Success message includes attachments folder
|
|
|
|
- **WHEN** new application is created successfully
|
|
- **THEN** the success message mentions the attachments folder
|
|
- **AND** provides guidance on what documents to place there
|
|
- **AND** indicates this folder is for CV, cover letter, certificates
|
|
|
|
### Requirement: Application Folder Structure
|
|
|
|
The system SHALL create a complete folder structure for each new application including metadata, input documents, and attachments.
|
|
|
|
#### Scenario: Complete folder structure created
|
|
|
|
- **WHEN** `/new-application` command is executed
|
|
- **THEN** the following structure is created:
|
|
```
|
|
applications/pending/[YYYY-MM-DD-Company-JobTitle]/
|
|
├── application.md
|
|
├── input/
|
|
└── attachments/
|
|
└── .keep
|
|
```
|
|
- **AND** application.md contains the template with metadata
|
|
- **AND** input/ folder is empty and ready for job posting documents
|
|
- **AND** attachments/ folder contains .keep file for version control
|
|
|
|
### Requirement: User Guidance for Attachments
|
|
|
|
The system SHALL provide clear guidance on the purpose and usage of the attachments folder.
|
|
|
|
#### Scenario: Attachments folder purpose explained
|
|
|
|
- **WHEN** new application is created
|
|
- **THEN** the success message explains attachments folder is for "final documents ready to send"
|
|
- **AND** distinguishes it from input/ folder (which is for "source materials and research")
|
|
- **AND** lists expected document types (CV, cover letter, certificates, diplomas)
|
|
|
|
#### Scenario: Workflow guidance includes attachments
|
|
|
|
- **WHEN** user views success message after creating application
|
|
- **THEN** the workflow guidance mentions adding documents to attachments/ after generation
|
|
- **AND** indicates attachments/ folder is checked by `/write-application-email` command
|