Agent skill

Project Life

Единый скилл ведения задач и жизни проекта: идеи/туду → планы/roadmap → раны → артефакты → прогресс/уроки.

Install Project Life

skills CLI

$ npx skills add VKirill/claude-lane-stack --skill project-life -a claude-code

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

GitHub CLI

$ gh skill install VKirill/claude-lane-stack project-life --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/VKirill/claude-lane-stack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/lane-stack/skills/project-life .claude/skills/project-life && 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/

Paste into Claude Code

Install the "project-life" agent skill from https://github.com/VKirill/claude-lane-stack/tree/main/plugins/lane-stack/skills/project-life into .claude/skills/project-life/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-life", 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

$skill-installer install https://github.com/VKirill/claude-lane-stack/tree/main/plugins/lane-stack/skills/project-life

Type 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.

skills CLI

$ npx skills add VKirill/claude-lane-stack --skill project-life -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install VKirill/claude-lane-stack project-life --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/VKirill/claude-lane-stack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/lane-stack/skills/project-life .agents/skills/project-life && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "project-life" agent skill from https://github.com/VKirill/claude-lane-stack/tree/main/plugins/lane-stack/skills/project-life into .agents/skills/project-life/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-life", 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.

skills CLI

$ npx skills add VKirill/claude-lane-stack --skill project-life -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install VKirill/claude-lane-stack project-life --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/VKirill/claude-lane-stack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/lane-stack/skills/project-life .cursor/skills/project-life && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "project-life" agent skill from https://github.com/VKirill/claude-lane-stack/tree/main/plugins/lane-stack/skills/project-life into .cursor/skills/project-life/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-life", 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

$ gemini skills install https://github.com/VKirill/claude-lane-stack.git --path plugins/lane-stack/skills/project-life

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add VKirill/claude-lane-stack --skill project-life -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install VKirill/claude-lane-stack project-life --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/VKirill/claude-lane-stack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/lane-stack/skills/project-life .gemini/skills/project-life && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "project-life" agent skill from https://github.com/VKirill/claude-lane-stack/tree/main/plugins/lane-stack/skills/project-life into .gemini/skills/project-life/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-life", 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.

GitHub CLI

$ gh skill install VKirill/claude-lane-stack project-life

Installs 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).

skills CLI

$ npx skills add VKirill/claude-lane-stack --skill project-life -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/VKirill/claude-lane-stack.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/lane-stack/skills/project-life .github/skills/project-life && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "project-life" agent skill from https://github.com/VKirill/claude-lane-stack/tree/main/plugins/lane-stack/skills/project-life into .github/skills/project-life/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-life", 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.

skills CLI

$ npx skills add VKirill/claude-lane-stack --skill project-life -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install VKirill/claude-lane-stack project-life --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/VKirill/claude-lane-stack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/lane-stack/skills/project-life .opencode/skills/project-life && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "project-life" agent skill from https://github.com/VKirill/claude-lane-stack/tree/main/plugins/lane-stack/skills/project-life into .opencode/skills/project-life/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-life", 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: project-life
GitHub stars: 122
Token cost: ~2.8k tokens
SKILL.md length: 1,270 words
Files: 5 (incl. references)
Skills in repo: 49
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Единый скилл ведения задач и жизни проекта: идеи/туду → планы/roadmap → раны → артефакты → прогресс/уроки.

Works in 4 steps: Create or open .agents/plans/items//… → Each decision → edit PLAN.md + dated… → Screenshots / notes → optional… → …
Agent Workflows work in your project
SKILL.md covers Info, The lifecycle (one mental model), Folder map and When to apply what, plus 7 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Project Life is an agent skill from VKirill/claude-lane-stack. Единый скилл ведения задач и жизни проекта: идеи/туду → планы/roadmap → раны → артефакты → прогресс/уроки. Use when user says туду, запиши, идея, backlog, потом, план, спланируй, планируем, пока план, не запускай, обсудим, roadmap, этапы, приоритеты, прогресс, урок, итоги — or todo, plan, planning, lesson, progress. Cold-start «где мы / handoff / продолж» is resume-project, not this skill. $ARGUMENTS exactly info prints the card.

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/info.md`, `references/memory.md` and `references/plans.md`).

It sits in Agent Workflows. The repository describes itself as: Multi-agent AI coding factory for one person — Claude Code PM + Codex/Qwen/Grok/Kimi/AGY writers, durable conveyor, auto-merge to main. The licence is MIT.

When your agent uses it

Agent Workflows work in your project

Example prompts

“/project-life”

Workflow steps

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

Create or open .agents/plans/items// (status: draft).
Each decision → edit PLAN.md + dated History. Chat is not the store.
Screenshots / notes → optional items//artifacts/; link from PLAN Links.
Ask the next scoped question. Do not invent a run or score a conveyor.

What it can do on your machine

Read from SKILL.md and the folder at commit 45fa19e. 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
No scripts in the folder and no shell commands in SKILL.md.
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

Project Life loads about 2.8k tokens when it runs, and up to ~5.9k if it reads all its reference files. Until then it costs about 112 tokens; SKILL.md has 1,270 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~112
When it runs · the whole SKILL.md, loaded when a task matches: ~2.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~5.9k

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 VKirill/claude-lane-stack at commit 45fa19e, republished under its MIT licence (© VKirill). 1,270 words, ~2,811 tokens.

Download SKILL.mdSave it as .claude/skills/project-life/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: project-life
description: Единый скилл ведения задач и жизни проекта: идеи/туду → планы/roadmap → раны → артефакты → прогресс/уроки. Use when user says туду, запиши, идея, backlog, потом, план, спланируй, планируем, пока план, не запускай, обсудим, roadmap, этапы, приоритеты, прогресс, урок, итоги — or todo, plan, planning, lesson, progress. Cold-start «где мы / handoff / продолж» is resume-project, not this skill. `$ARGUMENTS` exactly info prints the card.
argument-hint: [info]

Project life — one skill for tasks & project memory

Inside a Lane Pilot chat (LANE_PILOT_AGENT_TYPE set / tools lane_pilot_* present) the PM does not write PROGRESS, ROADMAP or plan ticks after a run: Lane Pilot's project-life helper does it (PROGRESS ≤40 lines, one CHANGELOG line, commit chore(progress)). The PM keeps .agents/todos/, .agents/plans/ and decision drafts. «делай» = lane_pilot_dispatch_writer (the whole plan at once, order through depends_on; no waves). A lesson = lane_pilot_lesson (rule, audience pm, writer or both — required; always only for a rule true of every writer task). Project facts that cannot be derived live in the hub memory (lane_pilot_memory_context, lane-memory search|context). run-init, run-finalize, memory-scribe, resume-project CLI and ~/.agents/bin/* below are the terminal harness.

Info

If $ARGUMENTS is exactly info, print references/info.md verbatim (Russian), then stop. Do not create a todo or plan unless the user already asked for that in the same message.

Everything lives in files under .agents/ (project) or ~/.agents/ (global). Durable files: English only. Chat may be Russian — answer in RU, write EN to disk. Never put secrets in any of these files. No orchestrator MCP. No todo_add / task CLI for ideas.

The lifecycle (one mental model)

text

idea ──► todo ──► plan ──► run ──► merged work
        (backlog) (map)   (execution)   │
                                        ▼
              memory: PROGRESS · lessons→hub · decisions · session-log · artifacts

Skipping layers upward is fine (small fix: idea → run). Skipping the memory update after work is not.

Folder map

text

<project>/.agents/
  todos/            # ideas backlog        → references/todos.md
    INDEX.md
    items/<YYYY-MM-DD-slug>/{README.md, AGENT.md, meta.yaml}
  plans/            # delivery map         → references/plans.md
    ROADMAP.md
    items/<YYYY-MM-DD-slug>/{PLAN.md, meta.yaml, artifacts/}
  runs/             # execution contracts  (skill lane-contract)
    <slug>/artifacts/<task>/...
  PROGRESS.md       # now / blocked / next → references/memory.md
  agent-notes/OPEN.md
  session-log/      # hooks own it — read only
  decisions/        # decision drafts; the docs pass publishes them to docs/decisions.md
<project>/.agents/plans/       # long-form strategy (NOT this layer)
<project>/docs/                # code documentation only, kept by the docs pass

Choose project root when cwd has .git/package.json/CLAUDE.md; use ~/.agents/... when user says «глобально» or cwd is home.

When to apply what

User says (≈)	Do	Reference
«занеси в туду / запиши / потом / не теряй»	Create/update todo item + INDEX	`references/todos.md`
chat about a todo, no «запиши»	Do not invent a todo; ask if they want it filed	—
«покажи туду / что в бэклоге»	Read INDEX + open items, answer in RU	—
«закрой / сделано / не надо»	status done/dropped + INDEX	`references/todos.md`
«планируем / пока план / не запускай / обсудим / спланируй / разбей на этапы»	Planning session — draft in `.agents/plans/`, no run	`references/plans.md`
«архитектор / новое приложение / новый сервис / спроектируем продукт»	Load app-architect. Same plan folder, living `artifacts/`. No run	skill `app-architect`
«что дальше по проекту» (already in session)	PROGRESS → ROADMAP → todos INDEX counts	—
«делай / реализуй / в работу / запускай ран»	Exit planning. Lane Pilot: `lane_pilot_dispatch_writer`. Terminal: spawn a run (`lane-contract`). Link it from the plan	—
run закончился зелёным	Terminal: tick plan task → refresh ROADMAP → rewrite PROGRESS. Lane Pilot: its helper does this	`references/memory.md`
поправили тебя / наступил на грабли	One lesson. Lane Pilot: `lane_pilot_lesson` with audience. Terminal: `lane-memory lesson "<rule>" --for pm\|writer\|both` (hub, not a file)	`references/memory.md`
зафиксировано крупное необратимое решение	draft in .agents/decisions/`<date>`-`<slug>`.md (the docs pass publishes it to docs/decisions.md)	`references/memory.md`
«итоги / конец сессии»	PROGRESS current, ideas filed as todos, no orphan runs	`references/memory.md`
«что делали / почему так / покажи отчёт»	Read session-log INDEX, run artifacts, findings — don't write them	—
«где мы / handoff / продолж» (cold start)	Skill `resume-project` (terminal: `~/.agents/bin/resume-project .`), not this file	—

Planning session

Stay here until the user says «делай / реализуй / в работу / запускай ран».

Triggers: «планируем», «пока план», «не запускай», «обсудим», «спланируй», «разбей на этапы», «только карта», «пока не в ран».

Create or open .agents/plans/items/<YYYY-MM-DD-slug>/ (status: draft).
Each decision → edit PLAN.md + dated History. Chat is not the store.
Screenshots / notes → optional items/<slug>/artifacts/; link from PLAN Links.
Ask the next scoped question. Do not invent a run or score a conveyor.

Forbidden until «делай»:

run-init, run-controller, run-supervisor, writers
Claude Code Plan mode and any write under ~/.claude/plans/
owns_paths / task YAML in this PLAN.md

If the host is already in Claude Plan mode: tell the user to switch to default and keep writing under .agents/plans/. Do not copy the harness file as the canon (you may quote it once into PLAN.md).

UI / visual initiative: Links must include docs/DESIGN.md. If it is missing, spawn design-lead (skill project-design) or draft DESIGN.md here — do not run-init a UI lane without it.

Exit: «делай» → Lane Pilot: lane_pilot_dispatch_writer; terminal: lane-contract / orchestrator-lanes Phase 0. Set plan status: active, link the run in the task table + meta.yaml.runs.

Decision guide (where does X go?)

X	Goes to
"we should someday…"	todo
"we will, in this order…"	`.agents/plans/` (delivery map)
long-form strategy / COCOON	`.agents/plans/` (not a coding queue)
"change code now"	run (never directly from todo/plan). Run has its own `PLAN.md` — execution DAG, not the map
"current state of reality"	PROGRESS (≤40 lines, rewrite not append)
"we got burned by…"	lesson → `lane_pilot_lesson` (Lane Pilot) / `lane-memory lesson` (terminal)
"we chose A over B forever"	draft in `.agents/decisions/` → published to `docs/decisions.md`
leftover debt / simplify later	`.agents/agent-notes/OPEN.md`
planning-session notes / screenshots	`.agents/plans/items/<slug>/artifacts/` (until a run exists)
reports, screenshots, receipts after a run	run artifacts (immutable, stay in the run)
"why is this code here"	session-log / findings (read only)

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

Linking discipline (what makes it ONE system)

Every hop leaves a back-link so any file leads to the full trail:

todo meta.yaml.related_runs ↔ plan meta.yaml.source_todos
plan task row run: link ↔ run notes its plan id
artifacts stay under .agents/runs/<slug>/artifacts/ — link load-bearing ones from PLAN.md Links and PROGRESS, never copy them around
Lessons and ADRs name their evidence (run, test, artifact)

Rituals

Session start: read .agents/PROGRESS.md (project rules reach you through CORE and the brief) → ROADMAP + todos INDEX counts only. Don't dump session-log into context. Cold start / unknown repo: skill resume-project (terminal CLI: ~/.agents/bin/resume-project .), then this skill for writes. Lane writers under a task contract do not write .agents/ (the PM does) — this skill's write rules are for the PM / interactive agent.

After a green run (terminal; in Lane Pilot its helper does this): tick plan task → refresh ROADMAP → rewrite PROGRESS (Now/Blocked/Next/Last verify) → a lesson only if corrected → ADR only if a durable fork was locked. After a wave of tasks, refresh PROGRESS once, not per micro-edit. Schema-v2: declare progress_now / close_next / close_open in run.yaml; run-finalize applies them — never guess stale checklist lines.

Session end: PROGRESS current; new ideas from chat filed as todos; session-log untouched (hooks own it).

Delegate the bookkeeping (Claude): when a ritual touches more than one file (PROGRESS + plan row + ROADMAP/INDEX, or filing todos), dispatch the memory-scribe subagent (Haiku) with 3–5 bullets of what happened — it formats and files per references/. Write lessons and ADRs yourself (judgment calls). Single quick append — just do it. Other CLIs: write directly.

Init a repo: ~/.agents/bin/project-memory-init <repo>; full passport: /project-onboard. If only root PROGRESS.md / LESSONS.md exist, init and session-ledger migrate them into .agents/.

Night audit: ~/.agents/bin/night-audit . or read AUDIT-*.md. Close OPEN items or spawn todos/runs.

Writing formats

Exact file templates live in this skill's references/ (todos.md, plans.md, memory.md). Stable paths: ~/.agents/skills/project-life/references/ (any CLI agent) or ~/.claude/plugins/marketplaces/claude-lane-stack/skills/project-life/references/ (Claude plugin). Read the matching file before creating or restructuring any of these; skip it for trivial appends you already know the shape of.

Ambiguity protocol

A vague ask («сделай красиво», unclear scope, two plausible readings) is not a license to guess. Order of preference:

Look it up yourself — code, PROGRESS, plans, todos, session-log.
Still ambiguous → ask the user a structured question with 2–4 options (Claude: AskUserQuestion), not an open-ended one.
Never silently pick an interpretation for destructive or scope-changing work. For trivial reversible work: pick the obvious reading, say so.

Keeping the layers right

Everything that matters is a file: todos, plans and results never live only in chat.
The project plan is .agents/plans/, not Claude Plan mode or ~/.claude/plans/; it is a delivery map, not a run queue, so it holds no task YAML or owns_paths (that is lane-contract) and no run starts during a planning session.
One layer per file: todo, plan and PROGRESS stay separate. PROGRESS is rewritten, not appended to; plans and todos link the runs that shipped them.
docs/ holds only the code documentation; plans, research and reports go to .agents/.
Production code changes go through a run (a writer dispatch), never straight from a todo or plan; ideas are files, not an orchestrator MCP todo_add.
Durable files are English and contain no secrets.

Files

SKILL.md and 4 other files (references) in plugins/lane-stack/skills/project-life of VKirill/claude-lane-stack.

SKILL.md
references/info.md
references/memory.md
references/plans.md
references/todos.md

Open the folder on GitHubat commit 45fa19e

Compare with similar skills

Project Life 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.

Project Life compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Project Life this skillVKirill/claude-lane-stack	122	—	~2.8k	Automated safety check: Pass	MIT	yesterday
MCP Server Builderanthropics/skills	180k	63 repos	~2.3k	Automated safety check: Pass	Apache-2.0	today
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official	38k	10 repos	~4.1k	Automated safety check: Notes	Apache-2.0	today
Using Superpowersfarm-fe/farm	5.6k	35 repos	~1.4k	Automated safety check: Pass	MIT	18 days ago
Executing Plans Inlineobra/superpowers	297k	2 repos	~5.1k	Automated safety check: Pass	MIT	today
Skill CreatorAzure/azqr	796	89 repos	~8.2k	Automated safety check: Pass	Apache-2.0	yesterday

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 63 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 10 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.
297k GitHub starsUsed in 2 repos~5.1k tokens
Agent WorkflowsAuto-check passed
Skill Creator
Azure/azqr
Official
Create new skills, modify and improve existing skills, and measure skill performance.
796 GitHub starsUsed in 89 repos~8.2k 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 7 repos~2.8k tokens
Agent WorkflowsAuto-check passed

Questions about Project Life

What does Project Life do?

Единый скилл ведения задач и жизни проекта: идеи/туду → планы/roadmap → раны → артефакты → прогресс/уроки. Project Life is an agent skill from VKirill/claude-lane-stack. Единый скилл ведения задач и жизни проекта: идеи/туду → планы/roadmap → раны → артефакты → прогресс/уроки.

When should I use Project Life?

Project Life fits situations like: agent Workflows work in your project.

How do I install Project Life in Claude Code?

Run `npx skills add VKirill/claude-lane-stack --skill project-life -a claude-code`. Or copy the skill folder (plugins/lane-stack/skills/project-life in VKirill/claude-lane-stack) into .claude/skills/project-life in your project. Claude Code loads it when a task matches its description.

How do I install Project Life in Codex?

Run `npx skills add VKirill/claude-lane-stack --skill project-life -a codex`. Or copy the skill folder (plugins/lane-stack/skills/project-life in VKirill/claude-lane-stack) into .agents/skills/project-life in your project. Codex loads it when a task matches its description.

Can I use Project Life 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 VKirill/claude-lane-stack --skill project-life -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/project-life, .gemini/skills/project-life, .github/skills/project-life and .opencode/skills/project-life in your project.

What does Project Life need to run?

SKILL.md names no scripts, command-line tools or credentials: Project Life is instructions for the agent only.

Does Project Life 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 Project Life 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 Project Life use?

Project Life is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Project Life use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.1k tokens, read only when the agent opens those files.

What are the alternatives to Project Life?

Skills that share tags, products or a category with Project Life: 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, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Project Life?

VKirill (a GitHub user) maintains it in VKirill/claude-lane-stack, which has 122 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 9, 2026.

Source: VKirill/claude-lane-stack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Project Life

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Project life — one skill for tasks & project memory

Info

The lifecycle (one mental model)

Folder map

When to apply what

Planning session

Decision guide (where does X go?)

Linking discipline (what makes it ONE system)

Rituals

Writing formats

Ambiguity protocol

Keeping the layers right

Files

Compare with similar skills

Similar skills

More from VKirill/claude-lane-stack

Related

Questions about Project Life