answer-application-questions

answer-application-questions

Fill an application form from the master profile — never invent. Hard rules: ../_shared/RULES.md. Paragraph answers reuse Communication verbs from ../tailor-resume/reference/action-verbs.md.

Inputs

Known-info gate (RULES §6): the job block (company/role/url) may be omitted — if absent, read jobs/current.json for it. All answers source from profile/master-profile.md; never re-ask the user for a fact (years_exp, work_auth, notice period, CTC) the profile already holds — flag a genuinely missing one rather than asking mid-form.

Batch mode (preferred for JobClaw / multi-question forms)

• --in resumes/<slug>.app-questions.in.json:

  {
    "job":    { "company": "...", "role": "...", "url": "..." },
    "region_hint": "US|IN",          // optional; else derive from job location / profile
    "questions": [
      { "id": "q1", "text": "Years of relevant experience?",           "type": "numeric" },
      { "id": "q2", "text": "Authorized to work without sponsorship?", "type": "yes_no"  },
      { "id": "q3", "text": "Notice period (in days)?",                "type": "short"   },
      { "id": "q4", "text": "Why this role?",                          "type": "paragraph", "max_chars": 600 },
      { "id": "q5", "text": "Work mode?", "type": "enum", "options": ["Remote", "Hybrid", "Onsite"] }
    ]
  }
  

• Profile = profile/master-profile.md.

Single mode (paste a question, get an answer)

• Paste the question; the skill infers type and answers in markdown.

Method

1. Region pack. Read knowledge/regions/<code>.md for phrasing — US: work-auth phrasing; IN: CTC / notice phrasing. For sponsorship verdicts specifically, defer to knowledge/work-authorization.md (judged against the job's region).

2. Read profile — preferences.* (notice_period, current_ctc, expected_ctc, willing_to_travel, earliest_start, needs_sponsorship), work_auth, years_exp, target.*, Notes / voice.