メニュー
Project lifecycle management — create, update, close, backlog rules, safe file operations. USE WHEN creating projects, closing projects, moving project files, managing project backlogs, or checking project status.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Resolve Obsidian Base files (.base) to see what the user sees in Obsidian. USE WHEN the user asks about Base views, queries vault notes, wants to see what a .base file shows, or needs filtered/sorted vault data. Wraps the obsidian-base CLI.
Vault conventions for wikilinks, frontmatter and tags. USE WHEN working with Obsidian vault files.
Obsidian template management — dual-tree creation, editing, rendering, frontmatter schemas, dynamic query blocks, Templater config updates. USE WHEN creating templates, editing templates, rendering templates, modifying template schemas, updating Templater folder mappings, adding query blocks, or checking template compliance.
Validate vault files against .mdschema files — structural checks on frontmatter, headings, and required sections. USE WHEN validate vault, check vault, vault lint, schema check, validate journals, validate memory.
Add [[wikilinks]] to a markdown document by matching terms against existing vault notes — body links and frontmatter keywords/related enrichment. USE WHEN a document needs wikilinks, terms should link to vault notes, knowledge graph needs enrichment, or enrich keywords.
[DEPRECATED] Use /ObsidianCLI instead. Obsidian Actions URI — atomic frontmatter props-set, rename with backlink updates, create notes, open notes. USE WHEN Obsidian Actions, actions URI, property set, rename note.
| name | ProjectManagement |
| version | 0.1.0 |
| description | Project lifecycle management — create, update, close, backlog rules, safe file operations. USE WHEN creating projects, closing projects, moving project files, managing project backlogs, or checking project status. |
Project lifecycle management — creating, updating, closing projects, backlog rules, and safe file operations.
Orchestration/Templates/Project.md.Projects/<Name>/<Name>.md (Folder Notes convention).project.status: planned for new projects, project.priority to appropriate level.Orchestration/Backlog.md if the project has actionable tasks.project.status: planned # planned | active | on-hold | completed
project.priority: Medium # Critical | High | Medium | Low
project.deadline:
project.owner:
project.team: []
project.objectives: []
Status and priority are scalars (single value), never arrays.
## Work log section at the bottom.### [[YYYY-MM-DD]] with sub-bullets for detail.project.status: completed and updated: date.Orchestration/Backlog.md (use [[Project#Section]] wikilinks to reference source)## Backlog or similar heading).Orchestration/Backlog.md using [[Project Name#Backlog]] section wikilinks.[[File#Heading]] links by globbing for the file and reading the heading section.When moving, renaming, or reorganizing project files:
mkdir -p the target directorycommand cp -R source to targetcommand diff source and target (for directories, verify file count)command rm the original only after verificationmv, cp, or rm — always prefix with commandSee imperative: [[Safe file operations in vault — copy verify remove never bare mv]]