skills.rest
podcodar
podcodarOFFICIAL
Explore all skills by this author →
WebsiteGitHub

project-files

Manage shared PLAN, TODO, SPEC, and SESSION files for multi-agent coordination.

7|1|Updated Jul 27, 2021
Search Tags:#project planning#agent coordination#architecture decisions#status tracking#session handoff#spec management#task queue
One-click install
npx skills add https://github.com/podcodar/webapp --skill project-files
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-files
Source: https://github.com/podcodar/webapp/tree/main/.agents/skills/project-files
Command: npx skills add https://github.com/podcodar/webapp --skill project-files

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents coordination drift by giving agents a shared, structured set of files that act as the single source of truth for plans, tasks, specs, decisions, sessions, status, and completed work.

Core Features & Use Cases

  • Centralized project state (PLAN/TODO): Maintain a high-level strategy and an always-current work queue that all agents can read and update.
  • Design clarity (SPEC/DECISIONS): Capture technical requirements and append-only architecture decisions so implementation agents follow the agreed design and future agents can trace rationale.
  • Smooth handoffs (SESSION/STATUS/CHANGELOG): Record what happened, what is happening now, blockers, and what was completed so the next session can resume quickly with continuity.
  • Use case: Start a complex multi-agent feature by creating PLAN.md, TODO.md, and SPEC.md, then delegate sub-tasks while continuously updating TODO.md and SESSION.md for handoff.

Quick Start

Use the project-files skill to initialize PLAN.md, TODO.md, SPEC.md, and then keep updating TODO.md and SESSION.md as your agents execute the work.

Frequently Asked Questions about project-files

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain project state consistency across multiple AI agents?▼

To maintain project state consistency across multiple agents, you use structured communication files like PLAN.md and TODO.md as a single source of truth for planning, execution, and handoff.

What is the best way to track architectural decisions during subagent delegation?▼

Tracking architectural decisions during subagent delegation requires an append-only DECISIONS.md file, allowing implementation agents to follow agreed designs and future agents to trace rationale.

How do I handle session handoff when delegating complex tasks to agents?▼

Handling session handoff for complex tasks involves recording completed work, current status, and blockers in SESSION.md and CHANGELOG.md files so the next session resumes quickly with full continuity.

Can I use markdown files for mandatory PLAN and TODO lifecycle management?▼

Yes, you can use markdown files like PLAN.md and TODO.md for mandatory lifecycle management by applying structured formats with state markers and append-only logs to manage task queues reliably.

Does multi-agent coordination work without a shared project specification file?▼

Multi-agent coordination without a shared project specification file risks coordination drift, as agents lack a single source of truth for technical requirements, status tracking, and agreed designs.

Related Skills

Explore More Product & Management Skills→
oaustegardoaustegard
137

versioning-skills

Initialize Git repositories and commit changes for skill directories.

Community
Basic
u9401066u9401066

doc-updater

Automate updates to README, CHANGELOG, API, and Memory Bank files.

Community
Basic
jacexhjacexh

subagent-driven-development

Dispatch fresh subagents per task with two-stage spec and code quality reviews.

Community
Advanced
timgranlundmarsdentimgranlundmarsden
2

Plugin Settings

Store and read per-project plugin settings from markdown files with YAML frontmatter.

Community
Advanced