mcpField
G
goals

goals

github.com/kriscard生産性1545 回インストール1 日前に更新
リポジトリ

goals について

月次、四半期、年次の目標を、現在の目標やプロジェクト、根拠を踏まえて設定・改訂するスキルです。期間と変更案を確認してから、現在のナレッジベースに書き込みます。

主な機能

  1. 01月次・四半期・年次の期間設定
  2. 02現行および前期の目標ノート確認
  3. 03プロジェクトとの目標の整合
  4. 04成果と確認可能な基準の定義
  5. 05変更案の提示・承認・検証

活用シーン

  1. 01新しい期間の目標設定
  2. 02現行目標の進捗確認
  3. 03状況変化に応じた目標の改訂
  4. 04期間を終えて次の期間を計画

インストール

コマンドをコピーしてターミナルで実行します。

$npx skills add https://github.com/kriscard/skills --skill goals

インストール後、Claude Code で/goalsを入力して読み込まれたか確認します。

README（原文）English

プロジェクトの README より

この README の日本語訳はまだありません。以下は英語の原文です。日本語の紹介はページ上部をご覧ください。

Goals

Set and revise forward-looking objectives. Weekly retrospectives belong to /weekly-review; this skill does not own weekly notes or weekly commitments.

1. Choose the horizon

Read ../vault/SKILL.md and the live AGENTS.md. Use $ARGUMENTS when it names monthly, quarterly, or yearly. Otherwise ask the user to choose one of those horizons.

Determine whether the user is:

  • creating the next period;
  • checking current progress;
  • closing a period and setting the next one.

Completion: the horizon, operation, and exact date range are confirmed.

2. Resolve live context

Discover the current goal path, filename convention, template, and dashboard from the live vault. Exclude archived templates. If the requested horizon has no active template, show a minimal proposed structure for approval rather than reviving an archived template or creating a parallel folder.

Read the relevant current and preceding goal notes, aligned projects, and source evidence supplied by the user. Use a dashboard as discovery, not as proof that every result is active.

Completion: the target note and evidence for each objective are known.

3. Draft objectives or adjustments

For each objective, confirm:

  • outcome;
  • checkable success criteria;
  • why it matters in this horizon;
  • aligned projects or milestones;
  • next review point.

During a check-in, label progress only from sourced milestones, elapsed dates, explicit blockers, or user confirmation. Ask whether a struggling objective should be adjusted, retired, or retained; never silently mark it failed.

Monthly objectives should advance current quarterly objectives. Quarterly objectives should support yearly direction when a yearly note exists. Do not invent alignment to fill a hierarchy.

Keep family and relationship goals qualitative as required by the schema; a checkable intention need not be a numeric target.

Completion: every proposed objective or adjustment is grounded in the chosen horizon and explicitly confirmed.

4. Preview, write, and verify

Show the target path and complete proposed change. After explicit approval, create from the resolved live template or update named sections through the vault safe-write flow. Reread and verify the written objectives, success criteria, and period.

Return the horizon, confirmed objectives or adjustments, aligned projects, next review point, and unresolved evidence gaps.

コメント

Markdown 対応