starworkspawn

starworkSpawn

Use this skill to turn the user's project idea into a StarWork Spawn Blueprint (workbench customization order).

A Spawn Blueprint is a small configuration package:

• blueprint.json: machine-readable structure and path configuration
• rules/*.md: project-specific Agent rules
• seed/**: optional initialization placeholder files

The Blueprint is executed by starwork spawn --blueprint . Unless the user explicitly asks to create files, this skill is only responsible for design and does not directly modify the user's Hub or target workspace.

Reference

When field details, validation rules, or command behavior are needed, read:

../../cli/spawn-blueprint-spec.md

Do not duplicate the full schema within the skill, to avoid drifting from the SPEC.

Workflow

1. Identify the workbench the user wants to create.

   • What is the project?
   • Is it a short-term lightweight project, or a long-term ongoing project?
   • Does it need items, decisions, handoff records, or cross-session tracking?

2. Choose the base mode.

   • For long-term projects, multi-step work, cross-session collaboration, or when item tracking is needed, use matter。
   • Only for lightweight projects that mainly need materials and deliverable output, use starter。

3. Determine whether a Blueprint or a Pack should be used.

   • For one-off project customization, use a Blueprint.
   • For structures that multiple projects or multiple users will reuse repeatedly, then suggest distilling them into a Pack.
   • Do not turn every directory preference into a Pack.

4. Design the workbench paths.

   • Define formal_source: confirm where outcomes or final deliverables are placed.
   • Define business_work_area: where current work is advanced.
   • Only add directories that will actually be used in the future.
   • Avoid decorative or ambiguous directories.

5. Write project rules.

   • rules/file-boundaries.md: where different kinds of information should each be placed.
   • rules/workflow.md: how the Agent advances work within the workbench.
   • rules/handoff.md: create only when cross-project or cross-session handoff is involved.

6. Produce or update files.

   • When the user is only discussing, describe the plan in text.
   • When the user asks for implementation, create the blueprint folder and files.
   • Use blueprint.json to manage structure, and Markdown to manage Agent rules; do not stuff long rules into JSON.

7. Explain how to execute.

   • First use starwork spawn --blueprint ... --dry-run to preview.
   • After confirmation, execute, or use --yes。
   • Finally use starwork doctor to check.

Output structure

When implementing the blueprint package, use:

<project>-blueprint/
├── blueprint.json
├── rules/
│   ├── file-boundaries.md
│   ├── workflow.md
│   └── handoff.md
└── seed/
    └── ...

handoff.md and seed/ are optional; do not create empty optional files.

Constraints

• blueprint.json Do not write Hub paths and target paths; they belong to CLI parameters.
• Do not overwrite user files.
• Do not modify the Kit source directory.
• Do not write directly to the Hub, unless through the registry registration behavior of starwork spawn .
• Do not delete AGENTS.md、.starwork/、.core-sync.json、_系统/、知识/ or skill links.
• Unless the user has a clear reason, prefer adding clear directories rather than renaming system directories.
• Markdown rules should be specific and actionable; avoid vague productivity advice.

Minimal example

{
  "schema": "starwork.spawn_blueprint.v0.1",
  "name": "内容产品官网",
  "project_id": "content-site",
  "base": {
    "mode": "matter",
    "kit": "satellite-matter",
    "language": "zh"
  },
  "paths": {
    "formal_source": "交付物/确认版本/",
    "business_work_area": "事项/"
  },
  "folders": [
    "资料库/",
    "草稿/",
    "会议纪要/",
    "版本记录/",
    "交付物/确认版本/"
  ],
  "agent_rules": [
    {
      "slot": "project.file_boundaries",
      "from": "rules/file-boundaries.md"
    },
    {
      "slot": "project.workflow",
      "from": "rules/workflow.md"
    }
  ]
}

Execute the command

Replace according to the actual path on the user's machine:

starwork spawn --hub <hub-path> --target <target-path> --blueprint <blueprint.json> --dry-run
starwork spawn --hub <hub-path> --target <target-path> --blueprint <blueprint.json> --yes
starwork doctor --target <target-path>