Skip to content

[Preset]: Add workflow-preset #2618

@bigsmartben

Description

@bigsmartben

Preset ID

workflow-preset

Preset Name

Workflow Preset

Version

1.0.3

Description

Adds design-aware planning artifacts and agent-native implementation handoff orchestration for larger Spec Kit features.

The preset keeps /speckit.plan and /speckit.tasks compatible with the core workflow while adding stable homes for object design, service sequencing, and test planning. It replaces /speckit.implement with a Core Agent, Vertical Planner Agent, and Worker Agent handoff contract so implementation can be executed in scoped worker contexts instead of one overloaded implementation prompt.

Author

bigsmartben

Repository URL

https://github.com/bigsmartben/spec-kit-workflow-preset

Download URL

https://github.com/bigsmartben/spec-kit-workflow-preset/archive/refs/tags/v1.0.3.zip

Release URL

https://github.com/bigsmartben/spec-kit-workflow-preset/releases/tag/v1.0.3

License

MIT

Required Spec Kit Version

=0.8.10.dev0

Required Extensions

None

Templates Provided

  • templates/plan-template.md - adds design artifact navigation to the plan template
  • schemas/speckit.implement.manifest.v1.schema.json - manifest contract for implementation handoff runs
  • schemas/speckit.implement.handoff.v2.schema.json - worker handoff contract
  • schemas/speckit.implement.receipt.v1.schema.json - worker receipt contract

Commands Provided

  • commands/speckit.plan.md - wraps core planning with optional class, sequence, and test design artifacts
  • commands/speckit.tasks.md - wraps task generation with optional design artifact awareness
  • commands/speckit.implement.md - runs agent-native handoff orchestration or executes exactly one worker handoff

Number of Scripts

0

Tags

planning, design, implementation, orchestration, handoff

Main Capability Areas

Plan enhancement

  • Adds class-diagram.md for internal object design: classes, interfaces, abstract types, services, repositories, adapters, factories, strategies, controllers, coordinators, composition, dependency direction, and design pattern participants.
  • Adds contracts/sequences.md for service and interaction flow: API calls, commands, events, async workers, external systems, retries, compensation, rollback, and failure branches.
  • Adds test-plan.md for validation design: test objectives, in/out of scope, test levels, data strategy, requirement traceability, and scenario matrix.
  • Keeps canonical Spec Kit boundaries intact: product requirements stay in spec.md, domain model details stay in data-model.md, interface schemas stay in contracts/, and executable validation guidance stays in quickstart.md.

Task generation enhancement

  • Lets /speckit.tasks consume the planning artifacts when present.
  • Uses object design, service sequence, and test-plan constraints to derive implementation, integration, orchestration, failure-handling, and validation tasks.
  • Preserves the existing checklist format and user-story organization.

Implementation handoff orchestration

  • Replaces broad /speckit.implement execution with agent-native handoff orchestration.
  • Core Agent owns lifecycle state, context-index.json, final handoff-manifest.json, worker dispatch, receipt review, tasks.md status commits, integration verification, and closeout.
  • Vertical Planner Agents each plan one vertical_capability, create shard plans, draft handoffs, draft context digests, and derive allowed read/write paths.
  • Worker Agents execute exactly one persisted speckit.implement.handoff.v2 handoff and write one speckit.implement.receipt.v1 receipt.
  • Handoffs record lifecycle stage, vertical capability, capability boundary, planner outputs, draft source, assigned task IDs, context digest path, allowed paths, validation commands, and forbidden actions.

Context Load / Reasoning Drift Mitigation

The preset is intended to reduce implementation-stage context overload, where a single agent run must keep product requirements, technical decisions, object design, service flows, test strategy, task ordering, and current code edits in one prompt. That load can cause reasoning drift: losing earlier design decisions, blurring task boundaries, reading unrelated documents, editing the wrong files, or marking tasks complete without enough validation evidence.

This preset mitigates that by:

  • Giving object design, sequence flow, and validation intent stable planning artifacts before tasks are generated.
  • Creating context-index.json so planning context is indexed without requiring every worker to read every source document.
  • Giving Worker Agents compact context digests instead of the full planning corpus.
  • Recording unresolved required context as context_gaps; workers must stop rather than guess or expand context on their own.
  • Restricting workers to allowed_read_paths and allowed_write_paths.
  • Keeping tasks.md writes centralized in the Core Agent after receipt review.

Testing Checklist

  • Preset installs successfully via specify preset add
  • Template resolution works correctly after installation
  • Documentation is complete and accurate
  • Tested on at least one real project

Submission Requirements

  • Valid preset.yml manifest included
  • README.md with description and usage instructions
  • LICENSE file included
  • GitHub release created with version tag
  • Preset ID follows naming conventions (lowercase-with-hyphens)

Verification Performed

  • python3 -m unittest tests/test_preset_contract.py in the preset repository: 36 passed
  • git diff --check: passed
  • GitHub Release v1.0.3 is published and is not draft/prerelease: https://github.com/bigsmartben/spec-kit-workflow-preset/releases/tag/v1.0.3
  • Fresh Spec Kit project install from https://github.com/bigsmartben/spec-kit-workflow-preset/archive/refs/tags/v1.0.3.zip: installed Workflow Preset v1.0.3 successfully
  • specify preset info workflow-preset: confirmed metadata, tags, 7 provided template/command entries, repository, license, and installed status

Related

Earlier catalog PRs were closed because community preset submissions are issue-first:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions