Skip to content

feat: 対話型パーソナルナレッジ基盤(Obsidian 向け personal-vault) - #23

Open
maouM-cmd wants to merge 7 commits into
mainfrom
cursor/personal-knowledge-dialogue-265e
Open

maouM-cmd wants to merge 7 commits into
mainfrom
cursor/personal-knowledge-dialogue-265e

Conversation

@maouM-cmd

@maouM-cmd maouM-cmd commented Aug 29, 2026 •

Copy link
Copy Markdown
Owner

Summary

対話で引き出した「自分のこと」を Obsidian 互換 Markdown として蓄積する基盤を追加しました。

  • personal-vault/ — MOC、5テーマノート、テンプレート、取り込み手順 README
  • @personal-knowledge Skill — 対話フロー、書き込みルール、5テーマの進行順序
  • knowledge-vault-qa.mjs — frontmatter 必須キー・MOC wikilink の検証

セッション進捗

  • 成り立ち セッション1(Q1回答済み): 就活→入社→AI駆動開発学習→NS研究室×NTTドコモ施策レコメンド案件。学習スタック(Dify, Docker, AWS, RAG, エージェント開発等)を記録

検証

node business-ops/scripts/knowledge-vault-qa.mjs
# → 0 errors
Open in Web Open in Cursor 

cursoragent and others added 6 commits August 29, 2026 06:12
- personal-vault/ に Obsidian 互換の MOC・5テーマノート・テンプレートを作成
- BUSINESS_MAP / AI_AGENT_MASTERY から仕事・目標ノートへ初期シード
- @personal-knowledge Skill で対話フロー・書き込みルールを定義
- knowledge-vault-qa.mjs で frontmatter と MOC リンクを検証
- 成り立ちテーマの初回セッションログを作成

Co-authored-by: maouM-cmd <maouM-cmd@users.noreply.github.com>
- 就活→入社→AI駆動開発学習→NS研究室×NTTドコモ施策レコメンド案件の流れを記録
- 学習中の技術スタック(Dify, Docker, AWS, RAG, エージェント開発等)を追記
- Q2・Q3は次回セッション用に未記入リストを残す

Co-authored-by: maouM-cmd <maouM-cmd@users.noreply.github.com>
- AI駆動開発指示へのワクワク、行動力の成長実感を記録
- 環境・メンタル面の原体験を追記(価値観テーマへリンク)
- 施策レコメンドの業務フロー(マニュアル→Dify→RAGAS)を記録

Co-authored-by: maouM-cmd <maouM-cmd@users.noreply.github.com>
- 見返す=目に見える成果、ハッカソン出場の決意
- 誠実さ・自分に嘘をつかないという譲れない価値観
- おじいちゃんへの尊敬、自信を持って語れる自分への志向
- 成り立ち・目標とビジョンへのクロスリンクを更新

Co-authored-by: maouM-cmd <maouM-cmd@users.noreply.github.com>
- 迷ったときの判断基準は誠実さ
- 恋愛・対人での取り繕いと疲れのパターンを記録
- ハッカソン方向性: 社会課題(SNS/ドーパミン)、自作プロダクトで証明
- 目標とビジョン・価値観へのクロスリンクを更新

Co-authored-by: maouM-cmd <maouM-cmd@users.noreply.github.com>
- 集中: ゴール明確・手順がわかる / 疲労: エラー・会談・責任ある仕事
- ハッカソン: 誹謗中傷対策・スクロール浪費防止のSNS設計
- エージェント目標: 工程の自律完遂 + 指示者の理解確認

Co-authored-by: maouM-cmd <maouM-cmd@users.noreply.github.com>
@maouM-cmd
maouM-cmd marked this pull request as ready for review August 29, 2026 10:23
- 幽霊はいない(観察・脳の錯覚)
- お酒に気をつけろ
- 自分のやりたいことをやれ

Co-authored-by: maouM-cmd <maouM-cmd@users.noreply.github.com>

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved based on present checks (business-ops and detect passed) with Cursor Bugbot not running on this PR. No approval policy required human review, and no reviewers were assigned.

Open in Web View Automation 

Sent by Cursor Approval Agent: Pull Request Approver

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9f04d42ccd

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

1. **就活** — 特に強い動機はなく「なんとなく」就職活動をした
2. **入社** — 会社に入社
3. **AI駆動開発への方向づけ** — 入社後、AI駆動開発について勉強するよう促された(当時の感情: **ワクワク**)
4. **現案件** — NS研究室 × NTTドコモの**施策レコメンド**案件に配属

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Anonymize client names before committing

In the normal no-explicit-approval path defined by this Skill, this records the identifiable organizations “NS研究室” and “NTTドコモ” in a Git-tracked note even though the same change requires company and person names to remain anonymized until the user explicitly approves them. The session log repeats the names, and no approval is recorded, so potentially confidential client/project information enters permanent Git history; replace these with anonymous labels unless approval has been obtained.

Useful? React with 👍 / 👎.

4. **仕事の進め方** — ツール、自動化、エージェント委任の境界
5. **目標とビジョン** — 短期・長期、「最強AIエージェントマスター」の具体像

**続きの検出:** 対象ノートの `status: draft` かつ「(対話で追記予定)」が残っていれば、前回の `sessions/` ログの「次回の問い」から再開する。

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Detect unfinished drafts using markers the notes actually contain

When a theme remains unfinished, this continuation condition never matches the supplied template or any of the committed core notes: they use blank list items or 未記入 checklists rather than the exact (対話で追記予定) marker. Consequently even status: draft notes with pending questions are not recognized as continuations, so the next invocation can restart or advance instead of resuming the previous log's 次回の問い; base the check on draft status plus the actual unfinished representation.

Useful? React with 👍 / 👎.

| 種別 | パス |
|------|------|
| 本ノート | `personal-vault/{テーマ}.md` |
| 対話ログ | `personal-vault/sessions/YYYY-MM-DD-{テーマ}.md` |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Add a unique session identifier to log filenames

If the same theme has two sessions on one calendar day—which the Skill explicitly permits—both resolve to this identical path. The later run therefore cannot create a distinct session log and may overwrite or conflate the earlier raw answers, while MOC links and “most recent log” selection cannot distinguish them; include the session number or a timestamp in the filename.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants