plans-and-specs

GitHub

提供计划与规范管理的详细操作指南,指导如何创建、链接和更新工作计划及需求文档。

skills/plans-and-specs/SKILL.md IgorWarzocha/opencode-planning-toolkit

Trigger Scenarios

用户要求制定计划或路线图 需要文档化需求或规格说明 读取或更新现有计划 标记工作完成 关联需求与计划

Install

npx skills add IgorWarzocha/opencode-planning-toolkit --skill plans-and-specs -g -y
More Options

Use without installing

npx skills use IgorWarzocha/opencode-planning-toolkit@plans-and-specs

指定 Agent (Claude Code)

npx skills add IgorWarzocha/opencode-planning-toolkit --skill plans-and-specs -a claude-code -g -y

安装 repo 全部 skill

npx skills add IgorWarzocha/opencode-planning-toolkit --all -g -y

预览 repo 内 skill

npx skills add IgorWarzocha/opencode-planning-toolkit --list

SKILL.md

Frontmatter
{
    "name": "plans-and-specs",
    "description": "This SKILL provides detailed instructions on how to use the planning plugin tools. MUST be loaded when:\n\nSituations:\n- User asks to create a plan, roadmap, or break down work into steps\n- User mentions specs, requirements, or standards that need to be documented\n- User references an existing plan that needs to be read or updated\n- User asks to mark work as complete or done\n- User wants to link requirements to a plan\n- User references a task that matches <available_plans>"
}

Plans and Specs

Plans are actionable work breakdowns stored as markdown with frontmatter. Specs are reusable requirements/documents. Plans link to specs via appendSpec. readPlan expands linked specs inline. After createPlan: MUST call appendSpec for each REPO scope spec (sequential), then ask about FEATURE specs. Before major work: MUST use readPlan to get plan + all linked specs. appendSpec: MUST be sequential calls, never batch/parallel. Specs MUST exist before appendSpec. markPlanDone: MUST ensure plan fully completed first.

Planning Workflow

  1. Check if plan already exists - if exact match, execute instead of creating
  2. createPlan with name, idea, description (3-5 words), steps (min 5)
  3. For each REPO spec returned: appendSpec(planName, specName) - sequential
  4. Ask user: "Want a FEATURE spec for this plan?"
  5. If yes: createSpec, then appendSpec
  6. Before work: readPlan to get full context

Spec Creation

createSpec with name, scope (repo/feature), reusable content.

Completion

markPlanDone only after all work verified complete.

Invalid name: Use [A-Za-z0-9-], max 3 words. Description error: 3-5 words, not overlapping name. Steps error: Need min 5 specific steps. Already exists: Use different name. Spec not found: Create spec first. Concurrent updates: appendSpec must be sequential.

Version History

  • b7b5025 Current 2026-08-20 06:57

Metadata

Files
0
Version
b7b5025
Hash
a02aac4b
Indexed
2026-08-20 06:57

trang chủ - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-09-12 22:35
浙ICP备14020137号-1 $bản đồ khách truy cập$