[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72T5RTDRSFXBAWHR5RV9DHW":3,"skill-same:01M72T5RTDRSFXBAWHR5RV9DHW":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M72T5RTDRSFXBAWHR5RV9DHW","ywc-project-mission",null,"(ywc) Use when capturing, reading, or curating a project's durable Mission \u002F North-Star, measurable Success Criteria, and Out-of-Scope non-goals — the \"why this project exists\" memory that frames every planning session. Triggers: \"프로젝트 미션 정리\", \"이 프로젝트 미션 기억해둬\", \"north star 정의\", \"success criteria 정리\", \"プロジェクトミッション\", \"project mission\", \"mission persistence\". Do not use for pre-intent idea exploration (use ywc-brainstorm), general project documentation (use ywc-project-docs), domain vocabulary (use ywc-ubiquitous-language), review preferences (use ywc-review-learnings), a single feature's plan (use ywc-plan), or spec-level review (use ywc-spec-validate).","yongwoon\u002Fywc-agent-toolkit","yongwoon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9317029?v=4","01M72SZSF6VKANKG5QTMV4V95S","01M72SZSG8HHC3W2CV5P7EJ5AH",8,"MIT","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-project-mission\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: ywc-project-mission\ndescription: >-\n  (ywc) Use when capturing, reading, or curating a project's durable Mission \u002F\n  North-Star, measurable Success Criteria, and Out-of-Scope non-goals — the\n  \"why this project exists\" memory that frames every planning session.\n  Triggers: \"프로젝트 미션 정리\", \"이 프로젝트 미션 기억해둬\", \"north star 정의\",\n  \"success criteria 정리\", \"プロジェクトミッション\", \"project mission\",\n  \"mission persistence\". Do not use for pre-intent idea exploration (use ywc-brainstorm), general project documentation (use ywc-project-docs), domain vocabulary\n  (use ywc-ubiquitous-language), review preferences (use ywc-review-learnings),\n  a single feature's plan (use ywc-plan), or spec-level review\n  (use ywc-spec-validate).\n---\n\n# ywc-project-mission\n\n**Announce at start:** \"I'm using the ywc-project-mission skill to read or update the project's durable mission, success criteria, and non-goals.\"\n\nThis skill produces or maintains `docs\u002Fproject-mission.md` — a per-project, accumulating record of the project's **durable** intent: the Mission \u002F North-Star (why the project exists), the measurable Success Criteria (what \"done\" looks like at the project level), and the Out-of-Scope non-goals (what the project deliberately will not do). It is the stateful-file sibling of `ywc-review-learnings`: instead of a one-off plan that is discarded after a feature ships, the mission lives as a committed, human-editable Markdown file that `ywc-plan` loads before clarifying any new request, so every planning session is framed by the same north-star rather than re-derived from scratch.\n\nIt operates in four modes: **read** (load the mission to frame planning), **update** (capture or revise mission \u002F criteria \u002F non-goals from a confirmed source), **list** (display the current mission), and **curate** (deprecate stale or superseded entries). Each entry records its provenance and date, so a future reader (or LLM) can tell a current commitment from an abandoned one.\n\n## Rationalization Defense\n\nWhen tempted to bypass a rule, check this table first:\n\n| Excuse | Reality |\n|---|---|\n| \"Write the mission I inferred from the code — confirmation is overhead\" | An unconfirmed mission silently frames *every* future planning session on this project. The mission is a durable commitment, not a guess; always present the ADD \u002F MODIFY \u002F DEPRECATE CHANGESET for one confirmation round before writing. |\n| \"This success criterion is obvious — skip the measurable form\" | A non-measurable criterion (\"be fast\", \"be usable\") cannot seed an Acceptance Criterion downstream and cannot tell `ywc-plan` whether a plan satisfies it. Every Success Criterion must be an observable, checkable done-condition. |\n| \"The new mission statement contradicts the old one — keep both\" | Two contradictory mission statements make planning non-deterministic. Newest-wins: deprecate the old entry with `~~strikethrough~~` + a superseded-by note, never silently delete — the history of *why* the direction changed is itself signal. |\n| \"Re-running `update` is harmless — just bump the date\" | A spurious `\u003C!-- updated -->` bump on an identical file produces noise in `git log` and falsely signals the mission moved. An `update` with an empty CHANGESET must be a no-op: no file write, no date bump. |\n| \"Record a feature-level task here so it's not forgotten\" | The mission file is for *durable* project intent, not the current sprint's task list. A transient task pollutes the north-star and ages into stale noise; route feature work to `ywc-plan` \u002F the task system, and reserve this file for commitments that outlive any single feature. |\n| \"Drop the provenance — the entry speaks for itself\" | Without provenance (`brainstorm` \u002F `plan \u003Cref>`) a reader cannot trace a criterion back to where it was agreed, so a stale entry can never be confidently retired. Record the source and date on every entry. |\n| \"Print the `@docs\u002Fproject-mission.md` activation prompt on every update so the user sees it\" | Repeating the CLAUDE.md activation reminder on each incremental update is noise. Print it **only** on first file creation — that is the one moment the reference does not yet exist. |\n\n**Violating the letter of these rules is violating the spirit.** A mission file full of unconfirmed, non-measurable, or undated entries frames every future planning session with noise instead of signal — the opposite of its purpose.\n\n## Arguments\n\n| Parameter | Format | Default | Description |\n|-----------|--------|---------|-------------|\n| `--mode` | `--mode read\\|update\\|list\\|curate` | auto-detect | Force a specific mode (see Mode Detection below) |\n| `--source` | `--source brainstorm\\|plan` | `brainstorm` | Where a new mission\u002Fcriterion comes from in `update` mode — `brainstorm` (a `ywc-brainstorm` handoff) or `plan` (a finalized `ywc-plan` success criterion). Recorded as provenance |\n| `--output` | `--output \u003Cpath>` | `docs\u002Fproject-mission.md` | Mission file path |\n| `--dry-run` | flag | off | Show the proposed CHANGESET without writing to disk |\n\n### Mode Detection (when `--mode` is omitted)\n\n| Condition | Auto-selected mode |\n|---|---|\n| Invoked by `ywc-plan` to frame a request, file exists | `read` |\n| User is stating durable intent (\"the mission is…\", \"success means…\", \"we will never…\") | `update` |\n| File absent, user wants to start a mission | `update` (creates the file with the first entry) |\n| User asks \"what is the project mission?\" | `list` |\n\n## Workflow\n\n### Mode: read — Load the Mission to Frame Planning\n\nInvoked before planning (typically by `ywc-plan` Step 1).\n\n1. **Read the file.** If `docs\u002Fproject-mission.md` is absent, return an empty mission and say so — never block planning on a missing mission file (NFR2 no-block invariant).\n2. **Emit a compact mission block** in the [Mission block format](#output-format): the Mission \u002F North-Star line, the active Success Criteria (skip `deprecated`), and the Out-of-Scope non-goals. Keep it tight — target ≤ ~25 lines (NFR1); a mission block that floods context degrades the planning it is meant to frame.\n\n### Mode: update — Capture or Revise the Mission\n\n1. **Read the existing file** in full (or note its absence to create it). Parse the current Mission, Success Criteria, and Out-of-Scope entries.\n2. **Gather the candidate** from the declared `--source`. Mission statements must be durable (outlive any single feature); Success Criteria must be **measurable** (an observable done-condition); Out-of-Scope entries must name the non-goal and the reason.\n3. **Classify against the existing file.** If a similar entry already exists, treat the candidate as a `MODIFY`, not a duplicate `ADD`. A candidate that contradicts an active entry is a `DEPRECATE` (old) + `ADD` (new), newest-wins.\n4. **Build the CHANGESET** for user confirmation: `ADD` \u002F `MODIFY` \u002F `DEPRECATE` lists, each showing its provenance and date. Do not write any entry the user has not confirmed.\n5. **Idempotency gate (AC15 \u002F NFR3).** If the confirmed CHANGESET is empty — the candidate content is identical to what the file already holds — **make no write**: do not touch the file, do not bump `\u003C!-- updated: DATE -->`. Report \"mission unchanged\" and stop.\n6. **Apply and echo.** Write confirmed changes, update the `\u003C!-- updated: DATE -->` header, append a `## Change Log` row, and print a `Mission updated` confirmation block listing exactly what changed.\n7. **CLAUDE.md activation prompt (first creation only).** The *first* time the file is created (it did not exist before this run), print the activation reminder so the mission actually reaches future planning:\n   ```text\n   ★ To activate this mission, add the following line to your CLAUDE.md so every\n     planning session (and every LLM session) loads it automatically:\n       @docs\u002Fproject-mission.md\n   ```\n   Print it only on first creation, not on every incremental update.\n\n### Mode: list — Display the Current Mission\n\nPrint the active mission, Success Criteria, and Out-of-Scope non-goals. Show deprecated entries only when explicitly asked. Useful before planning to sanity-check the north-star the planner will apply.\n\n### Mode: curate — Deprecate Stale \u002F Superseded Entries\n\n1. Read the file. Identify candidates: contradictory pairs, Success Criteria that no longer reflect the project, or entries the user reports as abandoned.\n2. Present a `DEPRECATE` list with the reason for each. On confirmation, mark with `~~strikethrough~~` and a `> deprecated YYYY-MM-DD: \u003Creason \u002F superseded-by #ID>` note. Never hard-delete — the history of *why* a direction was abandoned is itself a learning.\n\n## Output Format\n\nThe full mission-file specification (field rules, deprecation grammar, provenance grammar) is in [references\u002Fmission-format.md](references\u002Fmission-format.md).\n\n**`docs\u002Fproject-mission.md` (file) summary:**\n\n```markdown\n# Project Mission — [Project Name]\n\n\u003C!-- updated: YYYY-MM-DD -->\n\n## Mission \u002F North-Star\n- \u003Cdurable one-paragraph statement of what the project is and why>  (brainstorm, 2026-06-23)\n\n## Success Criteria\n| ID | Criterion (measurable) | Source | Added | Status |\n|----|------------------------|--------|-------|--------|\n| S001 | \u003Cobservable done condition> | brainstorm \u002F plan \u003Cref> | 2026-06-23 | active |\n\n## Out of Scope (durable non-goals)\n- \u003Cnon-goal> — \u003Creason>  (2026-06-23)\n\n## Change Log\n| Date | Change | Source |\n|------|--------|--------|\n| 2026-06-23 | Created mission + S001 | brainstorm |\n```\n\n**Mission block (read-mode emission, injected into planning):**\n\n```text\n## Project Mission\nNorth-Star: \u003Cdurable one-paragraph statement>.\nSuccess Criteria (2 active):\n  [S001] \u003Cobservable done condition>. (brainstorm, 2026-06-23)\n  [S002] \u003Cobservable done condition>. (plan #14, 2026-06-20)\nOut of Scope: \u003Cnon-goal>; \u003Cnon-goal>.\n```\n\n**`Mission updated` confirmation (update-mode emission):**\n\n```text\n✦ Mission updated (1 ADD, 0 MODIFY, 1 DEPRECATE)\n  + S004 [Success Criterion] — Median plan-to-first-task time under 10 minutes.\n        source: plan #21, 2026-06-23\n  ~ S002 deprecated — superseded by S004 (re-scoped from p95 to median).\n```\n\n## Validation\n\nBefore declaring complete:\n\n- [ ] The Mission \u002F North-Star statement is durable (outlives any single feature), not a feature description\n- [ ] Every active Success Criterion is measurable (an observable done-condition), not a vague aspiration\n- [ ] Every entry carries a `Source` (provenance) and a date (`Added` \u002F inline `YYYY-MM-DD`)\n- [ ] No two **active** entries contradict each other (the older was deprecated, not left to coexist)\n- [ ] The user confirmed the CHANGESET before any write (no inferred-and-written entries)\n- [ ] An `update` with no new content made no write and no `\u003C!-- updated -->` bump (idempotency)\n- [ ] `docs\u002Fproject-mission.md` is parseable Markdown with no broken table rows\n- [ ] `\u003C!-- updated: DATE -->` header reflects today's date (on a real write only)\n- [ ] A `Mission updated` confirmation was printed for update mode\n- [ ] On first file creation, the `@docs\u002Fproject-mission.md` CLAUDE.md activation prompt was printed once\n\n## Common Mistakes\n\n- **Writing an inferred mission without confirmation** — the single most damaging failure. An unconfirmed mission frames every future planning session; always confirm the CHANGESET first.\n- **Non-measurable success criteria** — \"be fast\" cannot seed an Acceptance Criterion or tell the planner whether a plan satisfies it. Make every criterion observable.\n- **Spurious date bumps** — re-running `update` on an identical file must be a no-op, not a fresh `\u003C!-- updated -->` line.\n- **Storing feature tasks as mission entries** — the mission is durable project intent, not the current sprint. Route transient work to `ywc-plan`.\n- **Hard-deleting a superseded entry** — the reviewer\u002Fplanner loses the record of why the direction changed. Deprecate with `~~strikethrough~~`, never delete.\n\n## Integration\n\n- **Upstream**: `ywc-brainstorm` (Step 6 Handoff offers to persist Mission + Success Criteria via `update --source brainstorm`), `ywc-plan` (Step 1 calls this skill in `read` mode to frame clarifying questions and seed Acceptance Criteria; may offer an `update --source plan` when a plan finalizes new durable criteria).\n- **Downstream**: `ywc-plan` consumes the read-mode Mission block; the file is also a natural `@docs\u002Fproject-mission.md` reference in `CLAUDE.md`.\n- **Pairs with**: `ywc-review-learnings` — same per-project stateful-file architecture (read\u002Fupdate\u002Flist\u002Fcurate, user-confirmed writes, first-creation activation prompt), different content domain (durable project intent vs review preferences).\n- **Do not confuse with**: `ywc-ubiquitous-language` (shared domain *vocabulary*, modes new\u002Fextract\u002Fupdate) — this skill stores the durable *intent*, not the term glossary.\n","# ywc-project-mission\n\n**Announce at start:** \"I'm using the ywc-project-mission skill to read or update the project's durable mission, success criteria, and non-goals.\"\n\nThis skill produces or maintains `docs\u002Fproject-mission.md` — a per-project, accumulating record of the project's **durable** intent: the Mission \u002F North-Star (why the project exists), the measurable Success Criteria (what \"done\" looks like at the project level), and the Out-of-Scope non-goals (what the project deliberately will not do). It is the stateful-file sibling of `ywc-review-learnings`: instead of a one-off plan that is discarded after a feature ships, the mission lives as a committed, human-editable Markdown file that `ywc-plan` loads before clarifying any new request, so every planning session is framed by the same north-star rather than re-derived from scratch.\n\nIt operates in four modes: **read** (load the mission to frame planning), **update** (capture or revise mission \u002F criteria \u002F non-goals from a confirmed source), **list** (display the current mission), and **curate** (deprecate stale or superseded entries). Each entry records its provenance and date, so a future reader (or LLM) can tell a current commitment from an abandoned one.\n\n## Rationalization Defense\n\nWhen tempted to bypass a rule, check this table first:\n\n| Excuse | Reality |\n|---|---|\n| \"Write the mission I inferred from the code — confirmation is overhead\" | An unconfirmed mission silently frames *every* future planning session on this project. The mission is a durable commitment, not a guess; always present the ADD \u002F MODIFY \u002F DEPRECATE CHANGESET for one confirmation round before writing. |\n| \"This success criterion is obvious — skip the measurable form\" | A non-measurable criterion (\"be fast\", \"be usable\") cannot seed an Acceptance Criterion downstream and cannot tell `ywc-plan` whether a plan satisfies it. Every Success Criterion must be an observable, checkable done-condition. |\n| \"The new mission statement contradicts the old one — keep both\" | Two contradictory mission statements make planning non-deterministic. Newest-wins: deprecate the old entry with `~~strikethrough~~` + a superseded-by note, never silently delete — the history of *why* the direction changed is itself signal. |\n| \"Re-running `update` is harmless — just bump the date\" | A spurious `\u003C!-- updated -->` bump on an identical file produces noise in `git log` and falsely signals the mission moved. An `update` with an empty CHANGESET must be a no-op: no file write, no date bump. |\n| \"Record a feature-level task here so it's not forgotten\" | The mission file is for *durable* project intent, not the current sprint's task list. A transient task pollutes the north-star and ages into stale noise; route feature work to `ywc-plan` \u002F the task system, and reserve this file for commitments that outlive any single feature. |\n| \"Drop the provenance — the entry speaks for itself\" | Without provenance (`brainstorm` \u002F `plan \u003Cref>`) a reader cannot trace a criterion back to where it was agreed, so a stale entry can never be confidently retired. Record the source and date on every entry. |\n| \"Print the `@docs\u002Fproject-mission.md` activation prompt on every update so the user sees it\" | Repeating the CLAUDE.md activation reminder on each incremental update is noise. Print it **only** on first file creation — that is the one moment the reference does not yet exist. |\n\n**Violating the letter of these rules is violating the spirit.** A mission file full of unconfirmed, non-measurable, or undated entries frames every future planning session with noise instead of signal — the opposite of its purpose.\n\n## Arguments\n\n| Parameter | Format | Default | Description |\n|-----------|--------|---------|-------------|\n| `--mode` | `--mode read\\|update\\|list\\|curate` | auto-detect | Force a specific mode (see Mode Detection below) |\n| `--source` | `--source brainstorm\\|plan` | `brainstorm` | Where a new mission\u002Fcriterion comes from in `update` mode — `brainstorm` (a `ywc-brainstorm` handoff) or `plan` (a finalized `ywc-plan` success criterion). Recorded as provenance |\n| `--output` | `--output \u003Cpath>` | `docs\u002Fproject-mission.md` | Mission file path |\n| `--dry-run` | flag | off | Show the proposed CHANGESET without writing to disk |\n\n### Mode Detection (when `--mode` is omitted)\n\n| Condition | Auto-selected mode |\n|---|---|\n| Invoked by `ywc-plan` to frame a request, file exists | `read` |\n| User is stating durable intent (\"the mission is…\", \"success means…\", \"we will never…\") | `update` |\n| File absent, user wants to start a mission | `update` (creates the file with the first entry) |\n| User asks \"what is the project mission?\" | `list` |\n\n## Workflow\n\n### Mode: read — Load the Mission to Frame Planning\n\nInvoked before planning (typically by `ywc-plan` Step 1).\n\n1. **Read the file.** If `docs\u002Fproject-mission.md` is absent, return an empty mission and say so — never block planning on a missing mission file (NFR2 no-block invariant).\n2. **Emit a compact mission block** in the [Mission block format](#output-format): the Mission \u002F North-Star line, the active Success Criteria (skip `deprecated`), and the Out-of-Scope non-goals. Keep it tight — target ≤ ~25 lines (NFR1); a mission block that floods context degrades the planning it is meant to frame.\n\n### Mode: update — Capture or Revise the Mission\n\n1. **Read the existing file** in full (or note its absence to create it). Parse the current Mission, Success Criteria, and Out-of-Scope entries.\n2. **Gather the candidate** from the declared `--source`. Mission statements must be durable (outlive any single feature); Success Criteria must be **measurable** (an observable done-condition); Out-of-Scope entries must name the non-goal and the reason.\n3. **Classify against the existing file.** If a similar entry already exists, treat the candidate as a `MODIFY`, not a duplicate `ADD`. A candidate that contradicts an active entry is a `DEPRECATE` (old) + `ADD` (new), newest-wins.\n4. **Build the CHANGESET** for user confirmation: `ADD` \u002F `MODIFY` \u002F `DEPRECATE` lists, each showing its provenance and date. Do not write any entry the user has not confirmed.\n5. **Idempotency gate (AC15 \u002F NFR3).** If the confirmed CHANGESET is empty — the candidate content is identical to what the file already holds — **make no write**: do not touch the file, do not bump `\u003C!-- updated: DATE -->`. Report \"mission unchanged\" and stop.\n6. **Apply and echo.** Write confirmed changes, update the `\u003C!-- updated: DATE -->` header, append a `## Change Log` row, and print a `Mission updated` confirmation block listing exactly what changed.\n7. **CLAUDE.md activation prompt (first creation only).** The *first* time the file is created (it did not exist before this run), print the activation reminder so the mission actually reaches future planning:\n   ```text\n   ★ To activate this mission, add the following line to your CLAUDE.md so every\n     planning session (and every LLM session) loads it automatically:\n       @docs\u002Fproject-mission.md\n   ```\n   Print it only on first creation, not on every incremental update.\n\n### Mode: list — Display the Current Mission\n\nPrint the active mission, Success Criteria, and Out-of-Scope non-goals. Show deprecated entries only when explicitly asked. Useful before planning to sanity-check the north-star the planner will apply.\n\n### Mode: curate — Deprecate Stale \u002F Superseded Entries\n\n1. Read the file. Identify candidates: contradictory pairs, Success Criteria that no longer reflect the project, or entries the user reports as abandoned.\n2. Present a `DEPRECATE` list with the reason for each. On confirmation, mark with `~~strikethrough~~` and a `> deprecated YYYY-MM-DD: \u003Creason \u002F superseded-by #ID>` note. Never hard-delete — the history of *why* a direction was abandoned is itself a learning.\n\n## Output Format\n\nThe full mission-file specification (field rules, deprecation grammar, provenance grammar) is in [references\u002Fmission-format.md](references\u002Fmission-format.md).\n\n**`docs\u002Fproject-mission.md` (file) summary:**\n\n```markdown\n# Project Mission — [Project Name]\n\n\u003C!-- updated: YYYY-MM-DD -->\n\n## Mission \u002F North-Star\n- \u003Cdurable one-paragraph statement of what the project is and why>  (brainstorm, 2026-06-23)\n\n## Success Criteria\n| ID | Criterion (measurable) | Source | Added | Status |\n|----|------------------------|--------|-------|--------|\n| S001 | \u003Cobservable done condition> | brainstorm \u002F plan \u003Cref> | 2026-06-23 | active |\n\n## Out of Scope (durable non-goals)\n- \u003Cnon-goal> — \u003Creason>  (2026-06-23)\n\n## Change Log\n| Date | Change | Source |\n|------|--------|--------|\n| 2026-06-23 | Created mission + S001 | brainstorm |\n```\n\n**Mission block (read-mode emission, injected into planning):**\n\n```text\n## Project Mission\nNorth-Star: \u003Cdurable one-paragraph statement>.\nSuccess Criteria (2 active):\n  [S001] \u003Cobservable done condition>. (brainstorm, 2026-06-23)\n  [S002] \u003Cobservable done condition>. (plan #14, 2026-06-20)\nOut of Scope: \u003Cnon-goal>; \u003Cnon-goal>.\n```\n\n**`Mission updated` confirmation (update-mode emission):**\n\n```text\n✦ Mission updated (1 ADD, 0 MODIFY, 1 DEPRECATE)\n  + S004 [Success Criterion] — Median plan-to-first-task time under 10 minutes.\n        source: plan #21, 2026-06-23\n  ~ S002 deprecated — superseded by S004 (re-scoped from p95 to median).\n```\n\n## Validation\n\nBefore declaring complete:\n\n- [ ] The Mission \u002F North-Star statement is durable (outlives any single feature), not a feature description\n- [ ] Every active Success Criterion is measurable (an observable done-condition), not a vague aspiration\n- [ ] Every entry carries a `Source` (provenance) and a date (`Added` \u002F inline `YYYY-MM-DD`)\n- [ ] No two **active** entries contradict each other (the older was deprecated, not left to coexist)\n- [ ] The user confirmed the CHANGESET before any write (no inferred-and-written entries)\n- [ ] An `update` with no new content made no write and no `\u003C!-- updated -->` bump (idempotency)\n- [ ] `docs\u002Fproject-mission.md` is parseable Markdown with no broken table rows\n- [ ] `\u003C!-- updated: DATE -->` header reflects today's date (on a real write only)\n- [ ] A `Mission updated` confirmation was printed for update mode\n- [ ] On first file creation, the `@docs\u002Fproject-mission.md` CLAUDE.md activation prompt was printed once\n\n## Common Mistakes\n\n- **Writing an inferred mission without confirmation** — the single most damaging failure. An unconfirmed mission frames every future planning session; always confirm the CHANGESET first.\n- **Non-measurable success criteria** — \"be fast\" cannot seed an Acceptance Criterion or tell the planner whether a plan satisfies it. Make every criterion observable.\n- **Spurious date bumps** — re-running `update` on an identical file must be a no-op, not a fresh `\u003C!-- updated -->` line.\n- **Storing feature tasks as mission entries** — the mission is durable project intent, not the current sprint. Route transient work to `ywc-plan`.\n- **Hard-deleting a superseded entry** — the reviewer\u002Fplanner loses the record of why the direction changed. Deprecate with `~~strikethrough~~`, never delete.\n\n## Integration\n\n- **Upstream**: `ywc-brainstorm` (Step 6 Handoff offers to persist Mission + Success Criteria via `update --source brainstorm`), `ywc-plan` (Step 1 calls this skill in `read` mode to frame clarifying questions and seed Acceptance Criteria; may offer an `update --source plan` when a plan finalizes new durable criteria).\n- **Downstream**: `ywc-plan` consumes the read-mode Mission block; the file is also a natural `@docs\u002Fproject-mission.md` reference in `CLAUDE.md`.\n- **Pairs with**: `ywc-review-learnings` — same per-project stateful-file architecture (read\u002Fupdate\u002Flist\u002Fcurate, user-confirmed writes, first-creation activation prompt), different content domain (durable project intent vs review preferences).\n- **Do not confuse with**: `ywc-ubiquitous-language` (shared domain *vocabulary*, modes new\u002Fextract\u002Fupdate) — this skill stores the durable *intent*, not the term glossary.\n",{"name":5,"description":7},"main","7e8ac872e53df8c89d75663e031626281a2a2f5c","claude-code\u002Fskills\u002Fywc-project-mission",1,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit","https:\u002F\u002Fgithub.com\u002Fyongwoon","https:\u002F\u002Fwww.webhani.com","2026-11-08 17:14:59",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add yongwoon\u002Fywc-agent-toolkit --skill ywc-project-mission",{"tool":37,"command":38},"bunx","bunx skills add yongwoon\u002Fywc-agent-toolkit --skill ywc-project-mission",{"tool":40,"command":41},"pnpm","pnpm dlx skills add yongwoon\u002Fywc-agent-toolkit --skill ywc-project-mission","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-project-mission\u002FSKILL.md",true,[45,51,55,59,63,67,70,74],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"evals\u002Fevals.json","REFERENCE","参考文档",4277,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-project-mission\u002Fevals\u002Fevals.json",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"README.en.md",3177,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-project-mission\u002FREADME.en.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"README.es.md",3746,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-project-mission\u002FREADME.es.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"README.ja.md",3567,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-project-mission\u002FREADME.ja.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"README.ko.md",3338,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-project-mission\u002FREADME.ko.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":69},"README.md","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-project-mission\u002FREADME.md",{"path":71,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":72,"sourceHtmlUrl":73},"README.zh.md",3357,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-project-mission\u002FREADME.zh.md",{"path":75,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fmission-format.md",4312,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fclaude-code\u002Fskills\u002Fywc-project-mission\u002Freferences\u002Fmission-format.md",[79,85,91,98,105,112],{"skillNo":80,"name":81,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M72TQ84GTCPCV2VJ778V17TW","missing-frontmatter","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fcodex-description-limit\u002Fmissing-frontmatter\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M72TQ6M4BFWE7P9EPW0GZDCM","malformed-frontmatter","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fcodex-description-limit\u002Fmalformed-frontmatter\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M72TQ3ESGKXZ4QRWGTX92BKJ","fixture-501-fail","(ywc) Use when aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Do not use for x.","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fcodex-description-limit\u002F501-fail\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M72TQ0HJ8H3R37J9WPWGKJZR","fixture-500-pass","(ywc) Use when aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Do not use for x.","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fcodex-description-limit\u002F500-pass\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":18},"01M72TPWNCC7NEYD0D9N12KSQS","ywc-worktrees","(ywc) Use when creating, auditing, pruning, or resolving git worktrees for isolated task workspaces, whether delegated from an executor or used standalone. Triggers: \"worktree 생성\", \"worktree audit\", \"worktree 정리\", \"worktree prune\", \"ywc-worktrees\", \"create worktree\". Do not use for branch creation\u002Fdeletion alone, PR creation (use ywc-create-pr), CI or merge delivery (use ywc-finish-branch), task orchestration (use ywc-sequential-executor or ywc-parallel-executor), or non-git isolation.","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-worktrees\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":18},"01M72TPRNR3E6QWB91GM98ABBV","ywc-wayfinder","(ywc) Use when a large or uncertain change needs multi-session discovery with a deterministic local map and exactly one active ticket before planning or implementation. Triggers: \"wayfinder\", \"길찾기\", \"discovery map\", \"multi-session discovery\", \"탐색 ticket\", \"経路整理\", \"探索マップ\", \"ywc-wayfinder\". Do not use for ordinary planning (use ywc-plan), idea clarification (use ywc-brainstorm), direct implementation, or tracker\u002Fdatabase writes outside the local Markdown map.","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-wayfinder\u002FSKILL.md",[],[]]