Finish prompd.json type field: skill vs workflow

[sbaker]

Summary

Complete the type field in prompd.json supporting 'skill' | 'workflow'. This determines how the project behaves in the ecosystem.

Type Definitions

workflow — Current default. Visual workflow canvas, .pdflow files, execution engine.

skill — Contains an MCP tool array and instructions on how to use the tools. Designed to be consumed by agents and other workflows as a composable unit.

What type controls

• Installation location — Skills and workflows install to different directories so they can be discovered by their consumers
• Registry filtering — Search/browse by type so users find what they need
• Project scaffolding — prompd init generates the right structure based on type
• Validation — Skills require MCP array + usage instructions; workflows require flow definitions

Implementation Scope

prompd-app

• Project creation wizard: choose skill vs workflow
• Filter installed packages by type
• Skill-specific UI (MCP tool list, usage instructions editor)

prompd-cli

• prompd init --type skill scaffolding
• Package validation rules per type
• Install to type-specific directories

registry

• Filter/search API: ?type=skill or ?type=workflow
• Registry UI: type badge on package cards, filter tabs

Notes

• The type field in manifest.json already exists loosely as a string (used by packaging). This formalizes the allowed values at the project level.
• Existing types in practice: "package" (CLI), "workflow" (frontend deployment), "node-template" (planned)
• Skills are the composable building blocks; workflows are the orchestration layer that consumes them