agentleFS
Sign inStart free
vibe-cokitvibe-cokit/claude-code/skills/vk-plan-archive/SKILL.md

vk-plan-archive

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

Write journal entries and archive specific plans or all plans

  • Deletes or force-pushes

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 6 are distinctive, and 10 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 10

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read and analyze the plans, then write journal entries and archive specific plans or all plans in the plans directory.

    line 8
  2. Very specific:

    If $ARGUMENTS provided → Use that path

    line 11
  3. Distinctive:

    Read the plan directory:

    line 18
  4. Very specific:

    Use AskUserQuestion tool to ask if user wants to document journal entries or not.

    line 23
  5. Distinctive:

    If user selects "Yes":

    line 25
  6. Very specific:

    Use Task tool with subagent_type="journal-writer" in parallel to document all plans.

    line 27
  7. Very specific:

    Keep journal entries in the ./docs/journals/ directory.

    line 29
  8. Very specific:

    Use AskUserQuestion tool to ask if user wants to proceed with archiving these plans, select specific plans to archive or all completed …

    line 32
  9. Very specific:

    Use AskUserQuestion tool to ask if user wants to delete permanently or move to the ./plans/archive directory.

    line 33
  10. Distinctive:

    Start archiving the plans based on the user's choice:

    line 36
  11. Very specific:

    Delete the plans permanently: rm -rf ./plans/<plan-1> ./plans/<plan-2> ...

    line 38
  12. Very specific:

    Use AskUserQuestion tool to ask if user wants to commit the changes with these options:

    line 41
  13. Very specific:

    Commit and push the changes (Use /vk-git-cp slash command)

    line 43
  14. Distinctive:

    After archiving the plans, provide summary:

    line 47
  15. Distinctive:

    IMPORTANT: Only ask questions about genuine decision points - don't manufacture artificial choices.

    line 55
  16. Distinctive:

    IMPORTANT: Ensure token efficiency while maintaining high quality.

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Your mission

Read and analyze the plans, then write journal entries and archive specific plans or all plans in the plans directory.

Plan Resolution

  1. If $ARGUMENTS provided → Use that path
  2. Else read all plans in the plans directory

Workflow

Step 1: Read Plan Files

Read the plan directory:

  • plan.md - Overview and phases list
  • phase-*.md - 20 first lines of each phase file to understand the progress and status

Step 2: Summarize the plans and document them with /vk-journal slash command

Use AskUserQuestion tool to ask if user wants to document journal entries or not. Skip this step if user selects "No". If user selects "Yes":

  • Analyze the information in previous steps.
  • Use Task tool with subagent_type="journal-writer" in parallel to document all plans.
  • Journal entries should be concise and focused on the most important events, key changes, impacts, and decisions.
  • Keep journal entries in the ./docs/journals/ directory.

Step 3: Ask user to confirm the action before archiving these plans

Use AskUserQuestion tool to ask if user wants to proceed with archiving these plans, select specific plans to archive or all completed plans only. Use AskUserQuestion tool to ask if user wants to delete permanently or move to the ./plans/archive directory.

Step 4: Archive the plans

Start archiving the plans based on the user's choice:

  • Move the plans to the ./plans/archive directory.
  • Delete the plans permanently: rm -rf ./plans/<plan-1> ./plans/<plan-2> ...

Step 5: Ask if user wants to commit the changes

Use AskUserQuestion tool to ask if user wants to commit the changes with these options:

  • Stage and commit the changes (Use /vk-git-cm slash command)
  • Commit and push the changes (Use /vk-git-cp slash command)
  • Nah, I'll do it later

Output

After archiving the plans, provide summary:

  • Number of plans archived
  • Number of plans deleted permanently
  • Table of plans that are archived or deleted (title, status, created date, LOC)
  • Table of journal entries that are created (title, status, created date, LOC)

Important Notes

IMPORTANT: Only ask questions about genuine decision points - don't manufacture artificial choices. IMPORTANT: In the last summary report, list any unresolved questions at the end, if any. IMPORTANT: Ensure token efficiency while maintaining high quality.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free