Personal Assistant
ailabs-393/ai-labs-claude-skills
This skill should be used whenever users request personal assistance tasks such as schedule management, task tracking, reminder setting, habit monitoring, productivity advice, time management, or…
Deliver non-trivial Personal Assistant work with explicit plan-only, sdd-only, implement-approved-spec, and full-lifecycle modes.
AGPL-3.0Auto-check passed
Install Sdd Lifecycle
$ npx skills add edonyzpc/personal-assistant --skill sdd-lifecycle -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install edonyzpc/personal-assistant sdd-lifecycle --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/sdd-lifecycle .claude/skills/sdd-lifecycle && rm -rf skills-srcUse ~/.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/
Install the "sdd-lifecycle" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/sdd-lifecycle into .claude/skills/sdd-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-lifecycle", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/sdd-lifecycleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add edonyzpc/personal-assistant --skill sdd-lifecycle -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install edonyzpc/personal-assistant sdd-lifecycle --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/sdd-lifecycle .agents/skills/sdd-lifecycle && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sdd-lifecycle" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/sdd-lifecycle into .agents/skills/sdd-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-lifecycle", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add edonyzpc/personal-assistant --skill sdd-lifecycle -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install edonyzpc/personal-assistant sdd-lifecycle --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/sdd-lifecycle .cursor/skills/sdd-lifecycle && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sdd-lifecycle" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/sdd-lifecycle into .cursor/skills/sdd-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-lifecycle", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/edonyzpc/personal-assistant.git --path .agents/skills/sdd-lifecycle--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add edonyzpc/personal-assistant --skill sdd-lifecycle -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install edonyzpc/personal-assistant sdd-lifecycle --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/sdd-lifecycle .gemini/skills/sdd-lifecycle && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sdd-lifecycle" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/sdd-lifecycle into .gemini/skills/sdd-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-lifecycle", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install edonyzpc/personal-assistant sdd-lifecycleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add edonyzpc/personal-assistant --skill sdd-lifecycle -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/sdd-lifecycle .github/skills/sdd-lifecycle && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sdd-lifecycle" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/sdd-lifecycle into .github/skills/sdd-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-lifecycle", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add edonyzpc/personal-assistant --skill sdd-lifecycle -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install edonyzpc/personal-assistant sdd-lifecycle --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/sdd-lifecycle .opencode/skills/sdd-lifecycle && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sdd-lifecycle" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/sdd-lifecycle into .opencode/skills/sdd-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-lifecycle", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sdd-lifecycle- GitHub stars
- 148
- Token cost
- ~1.8k tokens
- SKILL.md length
- 820 words
- Files
- 2
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Deliver non-trivial Personal Assistant work with explicit plan-only, sdd-only, implement-approved-spec, and full-lifecycle modes.
- Works in 6 steps: Verify approved product scope or… → Search the actual dependency surface… → Create/update Feature Home and Tracker;… → …
- Routed by pa-docs-lifecycle-manager
- SKILL.md covers Boundaries, Read Set, Artifacts and Plan And Design, plus 3 more sections
- Calls make
What it does
Sdd Lifecycle is an agent skill from edonyzpc/personal-assistant. Deliver non-trivial Personal Assistant work with explicit plan-only, sdd-only, implement-approved-spec, and full-lifecycle modes. Use when routed by pa-docs-lifecycle-manager or explicitly asked to plan, design, implement approved scope, continue an active track, or close it. Create Plan and SDD only when complexity requires them, stop plan-and-implement after validated implementation, and keep closeout, commit, push, tag, publish, and release separately authorized.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
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
- Routed by pa-docs-lifecycle-manager
- Explicitly asked to plan
- Implement approved scope
- Continue an active track
Example prompts
- “/sdd-lifecycle”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Verify approved product scope or explicit governance authority from current
- Search the actual dependency surface with rg.
- Create/update Feature Home and Tracker; register the Feature Home.
- Create a Plan only when its delivery/risk content would not fit concisely in
- Create an SDD only when the design criteria above apply. Verify every named
- Record compatibility, rollback, and a requirement-to-test mapping where
What it can do on your machine
Read from SKILL.md and the folder at commit 2c9e06d. 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:
make
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Sdd Lifecycle loads about 1.8k tokens when it runs. Until then it costs about 121 tokens; SKILL.md has 820 words of instructions outside code blocks.
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 2c9e06d, republished under its AGPL-3.0 licence (© edonyzpc). 820 words, ~1,750 tokens.
Download SKILL.mdSave it as
.claude/skills/sdd-lifecycle/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- sdd-lifecycle
- description
- Deliver non-trivial Personal Assistant work with explicit plan-only, sdd-only, implement-approved-spec, and full-lifecycle modes. Use when routed by pa-docs-lifecycle-manager or explicitly asked to plan, design, implement approved scope, continue an active track, or close it. Create Plan and SDD only when complexity requires them, stop plan-and-implement after validated implementation, and keep closeout, commit, push, tag, publish, and release separately authorized.
SDD Lifecycle
Boundaries
Choose the mode covering the full authorized request; complete its stop point
without pausing at intermediate modes. A still-applicable review-only,
analysis-only, read-only, no-file-changes, “只分析”, or “不要改文件”
request means zero writes.
| Mode | Allowed work | Stop point |
|---|---|---|
plan-only | Scope approved work; create a Plan only when phased/risky delivery needs one | Before implementation design/code |
sdd-only | Write or review source-verified implementation design | Before runtime edits |
implement-approved-spec | Create justified prerequisites, implement, test, review, fix, and validate | Validated implementation; no closeout/commit |
full-lifecycle | Delivery plus explicitly requested closeout | Contracts reconciled and process artifacts disposed |
“Plan and implement” is implement-approved-spec; it never implies closeout,
archive, or commit. If target resolution remains ambiguous after explicit
ID/slug, current-conversation package, and the only Active Package, ask one
target question and perform zero writes.
Read Set
Read AGENTS.md, the owning Product Spec or Governance Contract, the matching
Tracker, and nearby architecture/code/tests. Read North Star for product work.
Read Plan/SDD only when they exist or the change justifies creating them. Treat
Archive as historical evidence, not approval.
Artifacts
- Use exactly one authority lane: Product Decision/Spec for product behavior; Governance Contract for repo-only docs/checker/CI/release/Agent rules.
- Baseline Active Package:
README.md+tracker.md. - Add
plan.mdfor phased delivery, material dependencies, risk, rollback, or cross-session execution. - Add
sdd.mdfor multi-module design, shared infrastructure, behavior/data/ privacy/lifecycle changes, compatibility, migration, or non-trivial UI state. - Tracker is the only execution status and validation log. Active Registry and Feature Home contain links, not status mirrors.
- Enforce
1 Now + 1 Next: at most oneImplementing | Validating | Blockedpackage plus onePlannedpackage. AtValidated, continue already-authorized closeout; ask once only if closeout authority is missing. - Tracker
Current Snapshotis the cross-session handoff. Never create standalonehandoff*.mdorcloseout.mdin an Active Package. - Follow
docs/development/documentation-workflow.mdfor exact lifecycle and retention rules; do not duplicate its templates inside this skill.
Plan And Design
Before implementation:
- Verify approved product scope or explicit governance authority from current contracts and the conversation; do not ask again for an already-made choice.
- Search the actual dependency surface with
rg. For PA Agent/runtime/command work, apply the Command Architecture Contract. Map this task's material decisions, admission, state transitions and effects to owners and factual bases in the existing SDD/task record; do not copy a second definition or infer the intended architecture from local command code. - Create/update Feature Home and Tracker; register the Feature Home.
- Create a Plan only when its delivery/risk content would not fit concisely in Tracker.
- Create an SDD only when the design criteria above apply. Verify every named method, type, setting, command, locale key, and CSS class against source.
- Record compatibility, rollback, and a requirement-to-test mapping where relevant. Close or explicitly defer P0/P1/P2 design findings.
Missing Plan/SDD in implement-approved-spec is not a separate user approval
gate: create only what the implementation genuinely requires. Stop if product
scope or risk acceptance is unresolved.
Show full SKILL.md (348 more words)Show less
Implement And Validate
For each behavior slice:
implement -> focused validation -> review -> fix -> verifyKeep the Tracker current and use existing module boundaries. Before a slice,
map its REQ/AC or risk to the change, minimum sufficient evidence, pass
condition, and rerun/expansion trigger. Follow Validation Planning And Reuse
and Test Failure Diagnosis in AGENTS.md; add tests for uncovered behavior
or regression risk, and select the correct source/tooling/artifact group.
Satisfy the Local Validation Gate at the justified scope, reusing covered
checks only with verified inputs/results. Use PA review/follow-up skills for
implementation review; fix-driven verification covers the affected risk.
Accept responsibility conformance before implementation/green tests. Separate deterministic harness, actual-model semantics/recovery and real-app evidence according to the affected boundary; fixtures cannot prove model generalization.
Retain required broad and app/device gates at each phase exit. For app proof,
use make deploy or the eligible current-build reuse target under AGENTS.md
Local Deployment, then observe the affected behavior. Do not claim app or iOS
validation without observed evidence; docs/skills-only work uses the docs gate.
Closeout
Enter only in full-lifecycle or after explicit close/archive intent.
- Reconcile actual behavior, current Product/Architecture/Governance contract, Tracker, and release state.
- Record final checks, residual risk, and artifact disposition in Tracker; move unresolved work to Backlog.
- Absorb durable outcomes into current contracts/tests.
- Delete Feature Home, Tracker, Plan, SDD, handoff, and round-by-round logs after absorption unless one contains unique evidence.
- Retain only a compact closeout or evidence document when a current authority
needs the historical rationale. Place it in
docs/archive/<year>/and link it from that authority; do not preserve a complete package by default. - Update the link-only Active Registry and run docs validation.
If a selected archive path exists, fail closed before mutating source state; do not overwrite, merge, auto-suffix, or partially move it.
Git Boundary And Output
Do not stage, commit, push, tag, publish, or release without explicit authority.
For a requested local commit, inspect status and focused diffs, stage only the
intended files, use a signed-off Conventional Commit, and add no
Co-Authored-By trailer.
Report the selected mode, artifacts justified or omitted, validation performed, open decisions, residual risk, and the exact stop point.
© 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/sdd-lifecycle of edonyzpc/personal-assistant.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 2c9e06d
Compare with similar skills
Sdd Lifecycle 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sdd Lifecycle this skilledonyzpc/personal-assistant | 148 | — | ~1.8k | Automated safety check: Pass | AGPL-3.0 | |
| Personal Assistantailabs-393/ai-labs-claude-skills | 454 | — | ~4.9k | Automated safety check: Pass | MIT | |
| Generic Assistantmastra-ai/mastra | 29k | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Adding Warehouse Person PropertiesPostHog/posthog | 40k | — | ~2.9k | Automated safety check: Pass | Custom licence | |
| N8n Docs Assistantn8n-io/n8n | 207k | — | ~550 | Automated safety check: Pass | Custom licence | |
| Build A Personal Skill From HistoryTHU-MAIC/OpenMAIC | 40k | — | ~678 | Automated safety check: Pass | MIT |
Similar skills
Generic Assistant
mastra-ai/mastra
Fallback authoring playbook for building general-purpose personal assistant agents that do not fit a more specific archetype.
- Official
Adding Warehouse Person Properties
PostHog/posthog
Sync columns from a synced data warehouse table onto PostHog person or group properties, so warehouse data becomes usable anywhere person and group properties already work: feature flag targeting…
- Official
N8n Docs Assistant
n8n-io/n8n
Answers n8n product, setup, credential, node, hosting, API, and usage questions from current n8n docs.
Build A Personal Skill From History
THU-MAIC/OpenMAIC
Derives a reusable personal skill for course-making from a representative sample of the user's own past classrooms and chat history, confirmed with them before saving.
Sdd
WrongStack/WrongStack
A skill your agent uses when the user wants a written spec, acceptance criteria, or a task graph before a non-trivial implementation, or runs the WrongStack /sdd workflow.
More from edonyzpc/personal-assistant
All 19 skills in this repoObsidian Dataview
edonyzpc/personal-assistant
Dataview plugin query syntax, inline expressions, DataviewJS API, and common vault analysis patterns.
Obsidian Test Vault Smoke
edonyzpc/personal-assistant
Validate Personal Assistant runtime and UI changes in the repo-local Obsidian test vault.
Obsidian Community Check
edonyzpc/personal-assistant
Trigger and inspect Obsidian Community checks for personal-assistant.
Pa Brat Beta Release
edonyzpc/personal-assistant
Manage Personal Assistant BRAT beta prerelease workflow. An agent skill from edonyzpc/personal-assistant.
Pa Docs Lifecycle Manager
edonyzpc/personal-assistant
Maintain PA task records and documentation lifecycle. An agent skill from edonyzpc/personal-assistant.
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…
Questions about Sdd Lifecycle
What does Sdd Lifecycle do?
Deliver non-trivial Personal Assistant work with explicit plan-only, sdd-only, implement-approved-spec, and full-lifecycle modes. Sdd Lifecycle is an agent skill from edonyzpc/personal-assistant. Deliver non-trivial Personal Assistant work with explicit plan-only, sdd-only, implement-approved-spec, and full-lifecycle modes.
When should I use Sdd Lifecycle?
Sdd Lifecycle fits situations like: routed by pa-docs-lifecycle-manager; explicitly asked to plan; implement approved scope; continue an active track.
How do I install Sdd Lifecycle in Claude Code?
Run `npx skills add edonyzpc/personal-assistant --skill sdd-lifecycle -a claude-code`. Or copy the skill folder (.agents/skills/sdd-lifecycle in edonyzpc/personal-assistant) into .claude/skills/sdd-lifecycle in your project. Claude Code loads it when a task matches its description.
How do I install Sdd Lifecycle in Codex?
Run `npx skills add edonyzpc/personal-assistant --skill sdd-lifecycle -a codex`. Or copy the skill folder (.agents/skills/sdd-lifecycle in edonyzpc/personal-assistant) into .agents/skills/sdd-lifecycle in your project. Codex loads it when a task matches its description.
Can I use Sdd Lifecycle 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 sdd-lifecycle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sdd-lifecycle, .gemini/skills/sdd-lifecycle, .github/skills/sdd-lifecycle and .opencode/skills/sdd-lifecycle in your project.
What does Sdd Lifecycle need to run?
Going by SKILL.md and its folder, Sdd Lifecycle needs the command-line tools its instructions call (make).
Does Sdd Lifecycle access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Sdd Lifecycle 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 Sdd Lifecycle use?
Sdd Lifecycle 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 Sdd Lifecycle use?
About 1.8k tokens (SKILL.md is roughly 7k 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 Sdd Lifecycle?
Skills that share tags, products or a category with Sdd Lifecycle: Personal Assistant (ailabs-393/ai-labs-claude-skills, 454 stars), Generic Assistant (mastra-ai/mastra, 29k stars), Adding Warehouse Person Properties (PostHog/posthog, 40k stars) and N8n Docs Assistant (n8n-io/n8n, 207k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sdd Lifecycle?
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 8, 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.