MCP コネクタ

You are helping me draft a **Pairag task** as **one** JSON document I will paste into the official Pairag app (import / draft flow). The app performs full validation and review — your job is to follow the protocol exactly.

## Credentials and tools
- I am connected to **Pairag MCP** with scope **pairag.task.create** (confirm with **pairag_whoami** if needed).
- Call **pairag_task_create_json** once for the checklist and protocol URLs. If you already have a draft JSON string, pass it as **manifest_json** so the server can run a lightweight shape check (optional; it does not replace app validation).

## Mandatory reads (same revision)
Before writing JSON, **fetch and follow** both URLs returned by **pairag_task_create_json** (field semantics + canonical schema):
- English field reference (markdown)
- Canonical protocol JSON (**pairag-task-publish-v18.json**)

Do **not** invent enum values or field meanings — align with those documents.

## Output rules (hard requirements)
1. Respond with **exactly one** JSON **object** (RFC 8259), no markdown fences around it unless the host requires it — if you use a fence, the **inner content** must still be pure JSON.
2. Top-level keys must be **only** `manifest` and `stages` (snake_case).
3. `manifest.version` must be the string **"18.0"**.
4. Use **snake_case** for JSON keys as specified in the protocol.
5. **Snowflake IDs** (task public ids, stage ids, etc.): in hosts that stringify tool arguments, prefer **JSON strings** for very large integers to avoid IEEE-754 precision loss; follow the protocol examples.
6. **Acceptance criteria** inside the manifest (e.g. `agent_skills[].acceptance_criteria`) are binding for settlement after publish — write them clearly and testably.

## Task intent (fill in for the model)
- **Working title**:
- **One-line goal**:
- **Target user / industry** (if any):
- **Stages** (what happens in order, and what “done” means per stage):
- **Bounties / energy** (if known; otherwise say “use sensible placeholders and I will edit in the app”):
- **Location / language / tags** (if any):
- **Risks, constraints, out-of-scope**:

After you output the JSON, add a short note reminding me to paste it into the Pairag app, save draft, and submit for platform review when ready.