skills.rest
AGM1968
AGM1968COMMUNITY
Explore all skills by this author →
GitHub

plan-agent

Audit Git commits to generate PLAN.md and enrich Weave graph nodes.

Updated Feb 16, 2026
Search Tags:#automation#git-history#plan-agent#weave#graph-enrichment#plan-import
One-click install
npx skills add https://github.com/AGM1968/weave --skill plan-agent-agm1968
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-agent
Source: https://github.com/AGM1968/weave/tree/main/.claude/skills/plan-agent
Command: npx skills add https://github.com/AGM1968/weave --skill plan-agent-agm1968

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboarding an existing repository into Weave often requires many manual steps to map history, generate planning metadata, and sync with GitHub. plan-agent automates the cold-start graph enrichment to convert a repo's commit history into a fully enriched Weave graph with aliases, learnings, metadata, Mermaid graphs, and GitHub synchronization.

Core Features & Use Cases

  • Automates auditing of commits to map work into planned tasks.
  • Generates and imports PLAN.md to bootstrap the Weave graph and task structure.
  • Enriches nodes with aliases, learnings, and metadata; renders Mermaid graphs; and syncs with GitHub.
  • Ideal for onboarding existing repos or bulk-enriching a graph from commit history across multiple sprints.

Quick Start

Initialize the plan-agent workflow against your repository to start building the Weave graph from commit history.

Frequently Asked Questions about plan-agent

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

FAQPage Schema
How do I onboard an existing repository into Weave from commit history?▼

Automating Weave graph cold-start enrichment involves auditing repository commits, generating PLAN.md, enriching nodes with aliases and learnings, and syncing with GitHub to map history into planned tasks.

What is the best way to bulk-enrich a Weave graph across multiple sprints?▼

Bulk-enriching a Weave graph across multiple sprints is handled by auditing commit history to map work, importing PLAN.md, and enriching nodes with metadata and Mermaid graphs for the entire repository.

Do I need GitHub CLI authenticated to auto-enrich Weave graphs?▼

Yes, auto-enriching Weave graphs requires the GitHub CLI authenticated, Weave installed, a Git repository with history, and an initialized repository via wv-init-repo to sync correctly.

Can I auto-generate planning metadata from commit history for Weave?▼

Yes, planning metadata is auto-generated from commit history by creating and importing a PLAN.md file to bootstrap the Weave graph structure and map work into planned tasks.

When should I not use automated Weave graph enrichment for repositories?▼

Automated Weave graph enrichment should not be used for repositories lacking commit history, or when Weave is not installed, GitHub CLI is unauthenticated, or wv-init-repo has not initialized the repository.

Related Skills

Explore More Software Engineering Skills→
AnsteorraAnsteorra
6

beads

Manage tasks in a distributed, git-backed graph issue tracker.

Official
Intermediate
marcusgollmarcusgoll
91

epic-sprints

Generate sprint-plan.md with dependency graphs and locked OpenAPI contracts.

Community
Advanced
astoreyaiastoreyai
3

ww-visualize

Visualize World Weaver semantic data as Mermaid, ASCII, JSON, and DOT diagrams.

Community
Advanced
AGM1968AGM1968

weave-audit

Audit Weave graphs for integrity issues and generate remediation reports.

Community
Advanced