save-plan-docs
Use when the user wants an idea, prompt, request, or suggestion turned into a saved plan document in a `docs/` folder, especially when they want metadata such as start time, source question, creation duration, or the tool name recorded in both the file body and filename.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- save-plan-docs
- group
- writing-format
- summary
- Turn a suggestion into a plan doc with metadata and a tool-tagged filename.
- description
- Use when the user wants an idea, prompt, request, or suggestion turned into a saved plan document in a `docs/` folder, especially when they want metadata such as start time, source question, creation duration, or the tool name recorded in both the file body and filename.
03 SKILL.md 正文
Save Plan Docs
Create a plan document from the user's suggestion and save it under a docs/ directory.
This skill is general-purpose. It is not tied to any one repository or project layout beyond creating or using a docs/ folder in the working area.
What to capture
For each plan, record:
start_timeinput_questioncreation_time_secondsorcreation_durationtool_name
Also include the tool name inside the plan content itself.
File placement
Save the output in docs/. If docs/ does not exist, create it.
Use a filename that includes the tool name. Prefer this pattern:
docs/YYYY-MM-DD_HHMMSS_<tool-name>_plan.md
If the user wants a different naming convention, keep the tool name in the filename anyway.
Working method
- Record the start timestamp before drafting.
- Read the user's suggestion or question carefully.
- Convert it into a concrete plan.
- Measure how long the drafting took.
- Save the finished plan to
docs/using a tool-tagged filename.
Plan structure
Use this structure unless the user asks for another format:
# Plan
## Metadata
- start_time: <ISO-8601 timestamp>
- input_question: <user input, normalized only if needed for readability>
- creation_time_seconds: <elapsed seconds>
- tool_name: <tool name>
## Plan
1. <step>
2. <step>
3. <step>
## Notes
- <assumptions, constraints, or follow-ups>
Tool name
Use the executing assistant or tool name when it is clear from context. If no better value is available, use codex.
Output quality
Make the plan actionable. Prefer short steps, explicit assumptions, and minimal filler.
04 同仓库更多 Skills
maintainer-workflow-commands
Use when adding or auditing project commands for setup, development, tests, lint, dependencies, troubleshooting, or releases, and when making those commands discoverable through bin/workflows.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
wrap-up
Scan the current conversation and produce a structured session close-out: deferred items, open questions, decisions made, and the single clearest next action. Ends with a ready-to-paste "next session opener" prompt. Use this skill whenever the user says "/wrap-up", "/deferred", "wrap up this session", "what did we defer", "what's left", "end of session summary", or asks what to pick up next time.
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions