wishket-applylisted

# wishket-apply — Wishket Application & Proposal Drafting ## Flow ```mermaid flowchart LR A[Project ID/URL/scout report] --> B[Fetch get_project details] B --> C[Read profile.yaml + portfolios/] C --> D[Draft proposal] D --> E[Recommend portfolios to attach] E --> F[Save to proposals/ + Summary] F --> G{Confirmed apply?} G -- Yes --> H[Register to wishket-pipeline] ``` ## Step 1: Obtain Project Details - If the user provides a project ID or URL, retrieve details via `get_project`. - If given a scout report file, extract the project ID and call `get_project`. - If missing, search using `search_projects` and confirm with the user. - If `description` is already cached in the `state.db` cache under `seen[<id>]`, reuse it first to avoid the 5-second `Crawl-delay`. - Writing a proposal means the project is already at 관심. If `triage` is missing, suggest marking it Interested in `wishket-pipeline` first. ## Step 2: Gather Materials - `~/.wishket-radar/profile.yaml` (respect `WISHKET_PROFILE` override): tech stack, roles, notes. - Existing drafts in `~/.wishket-radar/portfolios/`: scan file headers (title, tech stack, core features) to determine relevance. - If the user provides extra requirement documents, use the extraction pattern from `wishket-portfolio` (PDF=Read, PPTX/DOCX/XLSX=unzip). ## Step 3: Draft Proposal Always produce **exactly two files**. Do not write a third `submit` copy. | File | Role | Format | |---|---|---| | `draft.md` | Local