SpreadWorks Inc.
Official@spreadworks · Japan
Offers specialized orchestration for Software Delivery Document (SDD) lifecycle management, state reconstruction, and repository synchronization.
Agent Skills by SpreadWorks Inc.
Showing 8 vetted skills indexed across 1 GitHub repositories.
sdd-forge.flow-sync
Sync documentation with the current codebase using the sdd-forge CLI.
sdd-forge.flow-auto-on
Enable autoApprove to advance the SDD flow and dispatch to the next skill.
sdd-forge.flow-finalize
Execute commit, merge, and cleanup actions to finalize software delivery workflows.
sdd-forge.flow-plan
Formalize end-to-end software planning workflows from requirements through test planning.
sdd-forge.flow-resume
Reconstruct SDD flow state from flow.json and draft.md after context compaction.
sdd-forge.flow-impl
Orchestrate the SDD implementation workflow with gate checks and progress tracking.
sdd-forge.flow-auto-off
Disable autoApprove mode for the current SDD flow.
sdd-forge.flow-status
Query and present live SDD flow state with branches, worktree, steps, and commits.
Frequently Asked Questions About SpreadWorks Inc.
FAQPage SchemaWhat specific tasks does SpreadWorks enable for software teams?▼
SpreadWorks enables end-to-end software delivery planning, live state querying of branches and worktrees, and synchronization between documentation and source code. It manages the transition from requirements to test planning, implementation gate checks, and final commit/merge operations within the software delivery lifecycle.
Which personas benefit most from these technical capabilities?▼
Software engineers, release managers, and technical leads benefit from these capabilities. The system is designed for teams requiring strict traceability between documentation and code, as well as those needing to maintain consistent delivery states across complex, multi-step development environments.
What are the prerequisites for running these delivery functions?▼
Operation requires a structured repository environment containing flow.json and draft.md files for state persistence. Users must maintain a valid codebase context to allow the system to perform synchronization, gate checks, and commit actions effectively.