personal-assistant

Automatically route Personal Assistant ideas, decisions, planning, implementation, continuation, status, closeout, and archive work from ordinary language with minimal management load. Use for phrases such as "记录一个 PA idea", "继续推进", "先规划并实现", "需要我决定什么", or "帮我收尾". Send raw ideas to the Linear inbox without a B-xxx, promote only decision/version/cross-session research or execution work into repo docs with bidirectional links, honor explicit review-only or no-file-changes requests as zero-write, route runtime delivery to sdd-lifecycle, and keep commit, push, tag, publish, and release authorization explicit.

Manage Personal Assistant raw-idea intake, promotion, version planning, milestone rhythm, Linear issue hygiene, Chinese-first planning content, and product/milestone-level release readiness with minimal user management load. Use when explicitly invoked or routed by pa-docs-lifecycle-manager for phrases such as "记录一个 PA idea", "整理需要我决策的 PA 项", "帮我排 vNext 候选", or "PA 当前版本状态怎么样". Keep raw ideas in the Linear inbox without B-xxx, promote only decision/version/cross-session research or execution work with bidirectional repo links, and report Linear write failures honestly. For code-level readiness, use personal-assistant-review instead.

Orchestrate staged SDD work for non-trivial personal-assistant features with explicit plan-only, SDD-only, implement-approved-spec, and full-lifecycle authorization modes. Use when explicitly invoked or routed by pa-docs-lifecycle-manager to plan a feature, draft or review an SDD, implement approved product scope, track progress, or run an explicitly requested full lifecycle. Treat "plan and implement" as implement-approved-spec that may bootstrap missing Plan/SDD and stops after validated implementation; run closeout/archive only after explicit full-lifecycle or closeout intent. Keep commits separately authorized. For one-file bug fixes, use the focused review/fix/test path.

Trigger and inspect the Obsidian Community plugin review-branch scan for the personal-assistant plugin. Use when asked to run, trigger, poll, verify, or report the community.obsidian.md automated check for master, a branch, tag, or commit before Obsidian plugin release or publication.

Validate personal-assistant Obsidian plugin changes on a USB-connected iPhone using the iCloud Obsidian test vault, iPhone Mirroring when available, and Safari Web Inspector for real WKWebView DOM/CSS/console evidence. Use when asked to test, verify, debug, inspect, or visually confirm mobile/iOS behavior, touch interactions, Pagelet/Chat/Memory mobile UI, Safari Inspector probes, iCloud deployment, or real-device smoke after local Obsidian test-vault validation.

Validate the personal-assistant Obsidian plugin in the repo-local test vault using both fast CLI runtime smoke and full app UI/UX interaction smoke. Use when end-to-end verification is needed after UI/runtime changes, Pagelet work, Chat, Memory/VSS, Preview/Stats, settings, release-gate smoke, or visible layout/copy/interaction changes. For real-device iOS validation, use `obsidian-ios-real-device-smoke`. For community compliance scan, use `obsidian-community-check`.

Manage Personal Assistant BRAT beta prerelease workflow. Use when the user asks to prepare, explain, validate, publish, or follow up a BRAT beta/prerelease build; asks about beta branch management; wants to move tested development work into BRAT testing; or needs the feature branch to beta packaging branch to PR to master to stable release process.

Triage, confirm, fix, and validate code review findings in the personal-assistant repository after an agent team or human review. Use when the user asks whether review findings are real, whether they must be fixed, which findings are over-optimization, what architecture/product/program decisions are needed, or asks to implement and test the confirmed fixes after a review.

Review uncommitted or PR diffs in the personal-assistant Obsidian plugin with project-specific risk lanes, second-layer future-risk checks, severity discipline, subagent review routing, and validation boundaries. Use when the user asks for code review, agent team review, multi-angle review, review-first analysis, code-level release-readiness review, hidden side effects, compatibility risk, edge cases, security/performance risk, test gaps, maintenance cost, or comparison of review quality in this repository. For a cross-surface UI/UX design audit, use `ui-ux-design-audit`; for product/milestone-level release readiness via Linear, use `pa-linear-product-manager`.

Execute the stable release workflow for the Personal Assistant Obsidian plugin. Use when the user asks to prepare, validate, cut, or publish a stable release; asks for a stable release dry run or follow-up verification; or says "release", "发版", "publish stable", "cut release", "stable release", "发布正式版", or "正式发版". For BRAT beta prerelease builds, use `pa-brat-beta-release` instead.

Audit multi-surface UI/UX in the personal-assistant Obsidian plugin with the current PA framework, real interface evidence, structured scoring, adversarial finding verification, and product-decision routing. Use for design retrospectives, visual quality baselines, cross-surface consistency audits, accessibility/mobile evaluations, or requests such as "帮我看看设计" and "audit the UI". Default to audit-only; implement findings only when explicitly requested, and require separate authorization for commit or archive actions. For review of a current code diff or PR, use `personal-assistant-review` instead.

Templater plugin syntax, template commands, dynamic commands, user scripts, and startup templates. Use when the user asks about creating templates, inserting dynamic content, automating note creation, or writing Templater commands/user scripts.

Dataview plugin query syntax, inline expressions, DataviewJS API, and common vault analysis patterns. Use when the user asks about querying notes, creating tables from metadata, aggregating frontmatter data, or writing Dataview/DataviewJS code blocks.

Use when inspecting Obsidian Canvas .canvas JSON, nodes, edges, groups, cards, links, or layout structure.

Use when inspecting Obsidian Bases files, formulas, filters, views, properties, or .base structure.

Use when explaining Obsidian markdown syntax, wikilinks, callouts, embeds, properties, tags, or block references.

Use when inspecting Obsidian callout types, malformed callouts, nested callouts, or callout taxonomy.

Use when inspecting frontmatter consistency, missing properties, property casing, tag spelling, or metadata drift.

Use when inspecting Obsidian plugin lists, plugin settings, disabled plugins, config folders, or possible unused plugin signals.

Use when inspecting unresolved wikilinks, backlinks, outgoing links, orphan notes, embeds, or vault link health.