projectstore-bind
openbooklet.com/s/projectstore-bindopenbooklet.com/s/[email protected]GET /api/v1/skills/projectstore-bindBind this project to an existing ProjectStore vault, or initialize and bind a new vault, using the harness-neutral core. Arguments: [vault-path] [--layout <name>] [--language <code>].
Create a new Architecture Decision Record (ADR) in the bound vault. Arguments: <title>.
Register or remove ProjectStore's shared agents block, inspect its Codex model overlay, or configure per-role models and efforts. Arguments: <register | unregister | status | configure>.
Regenerate code-map.md (epic â code overview) from frontmatter code_refs, or set an artifact's code_refs. The command is the write path â planner/reviewer only propose refs. Arguments: [set <epic-id | story-path> <ref> [refâ¦]].
Create a new concept note (definition, mental model, glossary entry). Arguments: <title>.
adversarial critic for projectstore artifacts (ADR / research / epic / story) and design proposals. Pre-commits to likely problems, verifies claims against source, rates assumptions, runs gap-analysis + pre-mortem, applies multi-perspective + self-audit + realist-check. An independent, fresh-context pass to avoid self-approval bias. Read-only, no sycophancy. Invoke after authoring/revising an artifact, before treating it final.
Diagnose the ProjectStore install and vault through the harness-neutral doctor; fixes remain previewed and approval-gated. Arguments: [--install | --vault] [--fix].
Create a new epic (with stories subfolder) in the bound vault. Arguments: <epic-id> <title>.
Regenerate graph.md â the vault link graph (nodes + typed edges) derived from body links and frontmatter relations. Compute â preview â approval â apply through the core.
After a new projectstore artifact is created via $projectstore-adr, $projectstore-research, or $projectstore-epic (and similar generative commands), suggest running $projectstore-review <path> to peer-review the artifact with a fresh critic agent before it's committed. Only suggest for artifact kinds whose authoring guide has default_review=true. Never auto-execute â always ask first.
Re-derive every derived view (kanban, folder-index READMEs, code-map, graph) from the vault's source of truth â the repair half of doctor's vault checks. Hand-edits can never permanently desync the board.
Create a new research note. Arguments: <title>.
STORY-CONFORMANCE reviewer for projectstore-bound projects â a narrow, vault-aware role, NOT a general code reviewer. Invoke AFTER writing code, BEFORE committing or marking a story done. Verifies the diff actually closes the story â per-acceptance-criterion evidence â then correctness / regressions / codebase-fit / tests, severity + confidence rated, self-audited. Proposes the story's code_refs update. Asked for spec drift on a named active spec, it checks that spec's contracts against its covered stories' code_refs instead and reports, per contract, holds / drifted / cannot tell. Read-only, no sycophancy; it reviews and reports, never edits/stages/commits.
Create a new ops runbook (step-by-step how-to with verification & rollback). Arguments: <title>.
Search the bound vault for a phrase â literal, bounded, grouped by folder. Arguments: <query> [--kind <type>] [--status <status>] [--limit <n>] [--case-sensitive] [--include-derived].
Create a spec (normative "how" covering one or more stories), or transition its status (draft â active â superseded). Arguments: <title> | activate <SPEC-ID> | supersede <SPEC-ID>.
Show what's bound, the active layout, what is in progress, and whether the derived views are fresh.
Explain ProjectStore status-line availability for Codex. This surface is unsupported and the skill never writes configuration. Arguments: on | off | status.
When communicating with the user about anything stored in the projectstore vault (epics, stories, ADRs, research, kanban, backlog), reference every artifact by its human title from frontmatter â never by session-invented shorthand. Name the parent epic for stories; include status/priority when discussing state or plans. Applies by default in bound projects to summaries, plans, and progress reports.
Vault artifacts are the shared vocabulary between the user, this session, *other* sessions, and the post-compact agent. A title written in a file can be grepped, linked, and recognized in Obsidian six months from now. A label invented mid-session ("T3", "P0-1", "the doctor story") dies with the sess
Auto-indexed from SmartAndPoint/ProjectStore
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.