# Send Plans Methodology to your agent
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
## Fast path
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
## Suggested prompts
### New install

```text
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
```
### Upgrade existing

```text
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
```
## Machine-readable fields
```json
{
  "schemaVersion": "1.0",
  "item": {
    "slug": "plans-methodology",
    "name": "Plans Methodology",
    "source": "tencent",
    "type": "skill",
    "category": "其他",
    "sourceUrl": "https://clawhub.ai/cramtek/plans-methodology",
    "canonicalUrl": "https://clawhub.ai/cramtek/plans-methodology",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadUrl": "/downloads/plans-methodology",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=plans-methodology",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "packageFormat": "ZIP package",
    "primaryDoc": "SKILL.md",
    "includedAssets": [
      "SKILL.md"
    ],
    "downloadMode": "redirect",
    "sourceHealth": {
      "source": "tencent",
      "slug": "plans-methodology",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-29T10:08:35.519Z",
      "expiresAt": "2026-05-06T10:08:35.519Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=plans-methodology",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=plans-methodology",
        "contentDisposition": "attachment; filename=\"plans-methodology-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null,
        "slug": "plans-methodology"
      },
      "scope": "item",
      "summary": "Item download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this item.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/plans-methodology"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    }
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/plans-methodology",
    "downloadUrl": "https://openagent3.xyz/downloads/plans-methodology",
    "agentUrl": "https://openagent3.xyz/skills/plans-methodology/agent",
    "manifestUrl": "https://openagent3.xyz/skills/plans-methodology/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/plans-methodology/agent.md"
  }
}
```
## Documentation

### Plans Methodology

Structured work tracking for individuals or multi-agent teams. Each agent maintains plans/ in their workspace.

### Directory Structure

plans/
  README.md
  draft/          # Being defined, not yet approved
  approved/       # Ready for execution
  in_progress/    # Currently executing
  completed/      # Done
  archived/       # Historical reference

Each plan is a folder: YYYY-MM-DD-plan-name/

### Plan Contents

YYYY-MM-DD-plan-name/
  specs/              # Problem statements, requirements
  proposal.md         # Why: justification, impact, risks
  design.md           # How: architecture, flows, decisions
  tasks.md            # What: checkboxes, owners, phases

### proposal.md

# Proposal: [Plan Name]

## Status
Draft | Submitted | Approved | Rejected

## Parent Plan
[agent]/plans/[state]/[plan-name] (if child plan)

## Problem
What problem are we solving?

## Proposed Solution
High-level approach.

## Impact
What changes? What improves?

## Cost / Effort
Time, resources, dependencies.

## Risks
What could go wrong?

## Decision
Approved by [name] on [date] | Rejected because [reason]

### design.md

# Design: [Plan Name]

## Overview
What are we building/doing?

## Architecture / Approach
How does it work? Diagrams, flows, decisions.

## Dependencies
What do we need? Other plans, external services, other agents.

## Constraints
Limitations, rules, non-negotiables.

## Open Questions
Things still to be decided.

### tasks.md

# Tasks: [Plan Name]

## Summary
Brief overview.

## Tasks

### Phase 1: [Name]
- [x] Task description -> Owner
  Completed YYYY-MM-DD. Notes.
- [ ] Task description -> Owner
  Details, acceptance criteria.
- [ ] Delegate to [Agent]: [what] -> [Agent]
  Child plan: [agent]/plans/[state]/[plan-name]

### Lifecycle

Draft - Specs written, proposal drafted
Approved - Proposal approved, design and tasks written
In Progress - Execution started
Completed - All tasks done
Archived - Kept for reference

Move the plan folder between state directories to change state.

### When to Create a Plan

Create when: multi-agent coordination needed, significant effort, multiple phases, needs approval, or progress tracking desired.

Skip for: quick tasks, simple lookups, routine operations.

### Approval Authority

Define your own hierarchy. Typical pattern:

Owner/CEO approves strategic plans
Lead agent can approve plans aligned with established vision
Sub-agents submit proposals to their lead for approval

Document your approval chain in your workspace's plans/README.md.

### Delegation

When delegating work to another agent:

Parent plan's tasks.md references the child plan path
Child plan's proposal.md references the parent plan path

Example in parent tasks.md:

- [ ] Delegate to [Agent]: implement feature X
  Child plan: [agent]/plans/in_progress/2026-02-20-feature-x

Example in child proposal.md:

## Parent Plan
[lead-agent]/plans/in_progress/2026-02-20-parent-plan

### On Session Start

Check plans/in_progress/ for active plans
Check plans/draft/ for plans awaiting action
Continue where you left off

### Granularity Tips

Not everything needs a plan. Use for significant, multi-step work.
A single agent working on a quick fix does not need a plan.
Plans shine when coordination, tracking, or approval is involved.
Keep plan documents concise. Verbose plans get ignored.
## Trust
- Source: tencent
- Verification: Indexed source record
- Publisher: cramtek
- Version: 1.0.0
## Source health
- Status: healthy
- Item download looks usable.
- Yavira can redirect you to the upstream package for this item.
- Health scope: item
- Reason: direct_download_ok
- Checked at: 2026-04-29T10:08:35.519Z
- Expires at: 2026-05-06T10:08:35.519Z
- Recommended action: Download for OpenClaw
## Links
- [Detail page](https://openagent3.xyz/skills/plans-methodology)
- [Send to Agent page](https://openagent3.xyz/skills/plans-methodology/agent)
- [JSON manifest](https://openagent3.xyz/skills/plans-methodology/agent.json)
- [Markdown brief](https://openagent3.xyz/skills/plans-methodology/agent.md)
- [Download page](https://openagent3.xyz/downloads/plans-methodology)