Development Toolkit
Install the common set for software work in one step. This package has no files of its own. It depends on four packages, and three of those depend on Workflow Support, so one install brings in five.
- Package ID:
development-toolkit - Depends on: Development, Planning, Project Documents, Flows and Scenarios
- Startup visibility: This package has no entries of its own. Required packages add the Memory categories and Work Records Pattern from Planning, the Documents category from Project Documents, and the
use-workflowentry from Workflow Support. The files behind those entries stay on demand.
These counts describe this package's own entries when their parent routes expose them in Entries and are read. Required packages add their own entries. Linked files stay on demand unless selected or required.
Install
Package files follow your installation choices. Essentials leaves out Templates, so Extension starters are skipped. Restore the Templates category if you want those starters.
From your installed Open Forge workspace, preview the package and its required packages:
open-forge extension install development-toolkit --dry-run
Review the plan. Then apply it:
open-forge extension install development-toolkit
The CLI installs required packages from the same catalogue. See the Extension guide for scripts using --automatic, updates, removal, or a local source.
Why it exists
These four packages are the common set for software work, and the Toolkit makes them one install. While the Toolkit is installed, you can't remove one of its packages on its own, because the Toolkit depends on it. If you want only some of them, install those individually instead.
What you get
| Package | Contribution |
|---|---|
| Project Documents | The Documents Memory category, document starters, and the Vision and Architecture workflows |
| Planning | Ideas, Analysis, Decisions, and Checkpoints Memory categories, the Work Records Pattern, starters, and the Planning workflow |
| Flows and Scenarios | User Flow, Scenario, Scenario Collection, and Run Record starters |
| Development | Development, Debugging, and Review workflows |
| Workflow Support | The use-workflow Skill that selects and guides the workflows above, and a starter for writing your own |
Separate choices
Core Templates, Collaboration, Observations and Handoffs, and Task Coordination aren't included. Add them individually if you want them.
Install individual packages instead when only part of the set is useful. A bundle selects capabilities. It doesn't make every convention mandatory.
Next: Install this package, or update and remove Extensions.