New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Pa Docs Lifecycle Manager

by edonyzpc in edonyzpc/personal-assistant

Maintain PA task records and documentation lifecycle. An agent skill from edonyzpc/personal-assistant.

AGPL-3.0Auto-check passedAgent Workflows

Install Pa Docs Lifecycle Manager

skills CLI
$ npx skills add edonyzpc/personal-assistant --skill pa-docs-lifecycle-manager -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install edonyzpc/personal-assistant pa-docs-lifecycle-manager --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pa-docs-lifecycle-manager .claude/skills/pa-docs-lifecycle-manager && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pa-docs-lifecycle-manager
GitHub stars
148
Token cost
~2k tokens
SKILL.md length
967 words
Files
2
Skills in repo
19
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Maintain PA task records and documentation lifecycle. An agent skill from edonyzpc/personal-assistant.

  • Works in 4 steps: Inspect git status --short, focused… → Read only the matching current… → Read the relevant section of → …
  • Explicit idea capture
  • SKILL.md covers Contract, Guard Material Decisions, Read Minimally and Route Intent, plus 4 more sections
  • Calls git and npm

What it does

Pa Docs Lifecycle Manager is an agent skill from edonyzpc/personal-assistant. Maintain PA task records and documentation lifecycle. Use for explicit idea capture, creating or updating execution records, authority changes, or closeout/archive. Ordinary discussion, read-only status lookup and local fixes use AGENTS.md and relevant existing contracts.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Agent Workflows. The repository describes itself as: A plugin that harnesses AI agents and streamlining techniques to help you automatically manage Obsidian. The licence is AGPL-3.0.

When your agent uses it

  • Explicit idea capture
  • Updating execution records
  • Authority changes
  • Closeout/archive

Example prompts

  • “/pa-docs-lifecycle-manager”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Inspect git status --short, focused diffs, and search by ID/slug/concept.
  2. Read only the matching current authority: Backlog/Discovery for intake,
  3. Read the relevant section of
  4. Read Archive only when a current authority cites historical rationale or a

What it can do on your machine

Read from SKILL.md and the folder at commit 4e57a31. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pa Docs Lifecycle Manager loads about 2k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 967 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from edonyzpc/personal-assistant at commit 4e57a31, republished under its AGPL-3.0 licence (© edonyzpc). 967 words, ~1,968 tokens.

Download SKILL.mdSave it as .claude/skills/pa-docs-lifecycle-manager/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
pa-docs-lifecycle-manager
description
Maintain PA task records and documentation lifecycle. Use for explicit idea capture, creating or updating execution records, authority changes, or closeout/archive. Ordinary discussion, read-only status lookup and local fixes use AGENTS.md and relevant existing contracts.

PA Docs Lifecycle Manager

Contract

Use this router only for task-record or documentation lifecycle work. Ordinary discussion, read-only status lookup and local fixes use AGENTS and existing contracts.

Act as a low-burden router. Infer lanes, IDs, paths, and status transitions; do not ask the user to operate the documentation system. Resolve routine choices and reuse still-applicable user authorization from the conversation. Ask only about unresolved product judgment, risk acceptance, target ambiguity, or missing implementation/Git/release authority; preserve release-specific timing rules.

An explicit review-only, analysis-only, read-only, no-file-changes, “只分析”, “不要改文件”, or equivalent request means zero writes. This guard overrides every route below. Quoted, historical, negated, and hypothetical phrases do not grant write authority.

Guard Material Decisions

  • Treat a named library, framework, API, architecture, or explicit product/data/media boundary in a user-provided spec or current authority as binding until explicitly superseded.
  • Analysis/design/implementation authority does not authorize silently replacing it, inventing a narrower or broader boundary, or treating an Agent inference as user approval.
  • Before production code or authoritative docs, separate explicit requirements, verified facts, inferences, and open decisions. A material deviation needs one compact decision card: original choice, evidence, options/tradeoffs, recommendation, and rollback.
  • Continue only after explicit user approval for a material deviation; routine compatible work continues within the existing authorization. An Agent-authored Accepted/Approved status or post-hoc Decision, SDD, test, or implementation cannot manufacture authority. If discovered later, label the deviation and ask whether to restore the original constraint or accept a new dated decision; never backdate approval.

Read Minimally

  1. Inspect git status --short, focused diffs, and search by ID/slug/concept.
  2. Read only the matching current authority: Backlog/Discovery for intake, Decision/Product Spec for product behavior, Governance Contract for repo tooling, and Tracker for execution status.
  3. Read the relevant section of docs/development/documentation-workflow.md; read a template only when creating that artifact.
  4. Read Archive only when a current authority cites historical rationale or a closeout must decide whether unique evidence deserves retention.

Do not preload Roadmap, every index, every contract, templates, or Archive.

Route Intent

IntentRouteStop point
Casual idea or feedbackDiscuss in chat; create no B-xxxZero repo writes
“记录 / 保存”Deduplicate; create or reuse one minimal Backlog rowDurable capture only
Analysis or discussionRead-only unless cross-session preservation is explicitFindings or a compact Discovery Brief
Product decision / version candidate / cross-session executionCreate or reuse B-xxx, then use the matching authority laneAuthority established
“先规划 / 不写代码”Create only artifacts justified by complexityStop before implementation
“实现 / 修复 / 先规划并实现”L0 for a narrow contract-restoring fix; otherwise route to sdd-lifecycleValidated implementation; no commit/closeout
“继续”Resolve explicit ID/slug, then current-conversation package, then the only active packageCurrent authorized phase
“收尾 / 关闭 / 归档”Reconcile evidence and apply the closeout retention ruleClosed/Cancelled/Superseded
Status / “需要我决定什么”Read current authority and return one compact decision cardRead-only brief

For continuation, if zero or multiple candidates remain after the ordered resolution above, ask one target question and perform zero writes.

Planning plus implementation selects sdd-lifecycle implement-approved-spec; it does not authorize closeout, commit, push, tag, publish, or release. Only explicit full-lifecycle or closeout language selects full-lifecycle.

Choose One Authority Lane

  • Product behavior, runtime, UI, data, privacy, or permissions: Accepted Decision + Product Spec.
  • Repo documentation, checker, CI/release tooling, or Agent workflow without product behavior changes: Current Governance Contract.
  • Narrow restoration of an existing contract: affected code/doc plus focused regression evidence; do not create lifecycle scaffolding.

Existing external tracker links are provenance only. Do not use an external tracker as the default inbox, planning mirror, state authority, or sync gate.

Show full SKILL.md (388 more words)Show less

Keep Delivery Lean

  • Tracker is the only delivery-status and execution authority.
  • Active Registry is link-only. Feature Home is a short routing page; neither mirrors Tracker status.
  • Enforce 1 Now + 1 Next: at most one Implementing | Validating | Blocked package and at most one Planned package.
  • When a Tracker reaches Validated, continue closeout if already authorized; otherwise ask one compact closeout question. Do not leave it as indefinite active work.
  • An Active Package starts with README.md and tracker.md.
  • Add plan.md only for phased, risky, or cross-session delivery.
  • Add sdd.md only when source-verified design is needed for behavior, data, lifecycle, compatibility, or multi-module change.
  • Tracker Current Snapshot is the cross-session handoff. Do not create standalone handoff*.md or closeout.md in an Active Package.
  • Route substantial implementation/review/smoke work to sdd-lifecycle.
  • Put out-of-scope findings in Backlog instead of silently expanding scope.

Closeout And Archive

Close only against real validation evidence and explicit closeout authority.

  1. Reconcile actual behavior with the durable Product/Architecture/Governance contract and Tracker.
  2. Move unresolved work to Backlog with a restart condition.
  3. Absorb final behavior, decisions, and validation into current durable contracts or focused tests.
  4. Delete process artifacts after absorption by default; record disposition in Tracker and do not create a separate closeout document.
  5. Archive only unique rationale, migration/release/incident evidence, or a compact final report that current source or documentation still cites. Do not archive a complete package merely because it existed.
  6. Keep delivered Governance Contracts current. Archive Cancelled/Superseded contracts only when their terminal rationale remains useful; a Superseded contract must identify its Current successor.

If a chosen archive destination already exists, fail closed: do not overwrite, merge, auto-suffix, or partially move content.

Decisions, Skills, And Output

Ask at most one ordinary decision at a time. Batch 3-5 cards only when the user explicitly requests a decision queue; keep it read-only until answered.

Use sdd-lifecycle for substantial delivery, PA review skills for code review, and the appropriate smoke/release skill only when the authorized phase needs it. Route an explicit commit request through codex-commit when available.

After docs changes run:

bash
npm run docs:check
git diff --check

This lifecycle gate is independent from version publication. Report its findings separately; lifecycle status must not block a beta or stable release.

Docs-only work does not require Build or Obsidian smoke. Report changed authorities, validation, unresolved decisions, and ungranted Git/release actions; do not explain the hierarchy unless asked.

© edonyzpc, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/pa-docs-lifecycle-manager of edonyzpc/personal-assistant.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 4e57a31

Compare with similar skills

Pa Docs Lifecycle Manager next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Pa Docs Lifecycle Manager compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pa Docs Lifecycle Manager this skilledonyzpc/personal-assistant148—~2kAutomated safety check: PassAGPL-3.0
MCP Server Builderanthropics/skills180k64 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k11 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official38k8 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 64 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    296k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

More from edonyzpc/personal-assistant

All 19 skills in this repo

  • Obsidian Dataview

    edonyzpc/personal-assistant

    Dataview plugin query syntax, inline expressions, DataviewJS API, and common vault analysis patterns.

    148 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

  • Obsidian Test Vault Smoke

    edonyzpc/personal-assistant

    Validate Personal Assistant runtime and UI changes in the repo-local Obsidian test vault.

    148 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed

  • Obsidian Community Check

    edonyzpc/personal-assistant

    Trigger and inspect Obsidian Community checks for personal-assistant.

    148 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

  • Pa Brat Beta Release

    edonyzpc/personal-assistant

    Manage Personal Assistant BRAT beta prerelease workflow. An agent skill from edonyzpc/personal-assistant.

    148 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed

  • Personal Assistant Review

    edonyzpc/personal-assistant

    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…

    148 GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed

  • Personal Assistant Review Followup

    edonyzpc/personal-assistant

    Triage, confirm, fix, and validate code review findings in the personal-assistant repository after an agent team or human review.

    148 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Pa Docs Lifecycle Manager

What does Pa Docs Lifecycle Manager do?

Maintain PA task records and documentation lifecycle. An agent skill from edonyzpc/personal-assistant. Pa Docs Lifecycle Manager is an agent skill from edonyzpc/personal-assistant. Maintain PA task records and documentation lifecycle.

When should I use Pa Docs Lifecycle Manager?

Pa Docs Lifecycle Manager fits situations like: explicit idea capture; updating execution records; authority changes; closeout/archive.

How do I install Pa Docs Lifecycle Manager in Claude Code?

Run `npx skills add edonyzpc/personal-assistant --skill pa-docs-lifecycle-manager -a claude-code`. Or copy the skill folder (.agents/skills/pa-docs-lifecycle-manager in edonyzpc/personal-assistant) into .claude/skills/pa-docs-lifecycle-manager in your project. Claude Code loads it when a task matches its description.

How do I install Pa Docs Lifecycle Manager in Codex?

Run `npx skills add edonyzpc/personal-assistant --skill pa-docs-lifecycle-manager -a codex`. Or copy the skill folder (.agents/skills/pa-docs-lifecycle-manager in edonyzpc/personal-assistant) into .agents/skills/pa-docs-lifecycle-manager in your project. Codex loads it when a task matches its description.

Can I use Pa Docs Lifecycle Manager in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add edonyzpc/personal-assistant --skill pa-docs-lifecycle-manager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pa-docs-lifecycle-manager, .gemini/skills/pa-docs-lifecycle-manager, .github/skills/pa-docs-lifecycle-manager and .opencode/skills/pa-docs-lifecycle-manager in your project.

What does Pa Docs Lifecycle Manager need to run?

Going by SKILL.md and its folder, Pa Docs Lifecycle Manager needs the command-line tools its instructions call (git and npm).

Does Pa Docs Lifecycle Manager access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Pa Docs Lifecycle Manager safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Pa Docs Lifecycle Manager use?

Pa Docs Lifecycle Manager is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pa Docs Lifecycle Manager use?

About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Pa Docs Lifecycle Manager?

Skills that share tags, products or a category with Pa Docs Lifecycle Manager: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pa Docs Lifecycle Manager?

edonyzpc (a GitHub user) maintains it in edonyzpc/personal-assistant, which has 148 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.

Source: edonyzpc/personal-assistant on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.