Software Production
Briefs, tasks and software delivery in linked projects, with optional core DUI.
Before you install · 0.2.0
What it touches, and what it needs
The author declared these for this release, and review checked them against what the stack does, including what its skills ask the agent to do. They are declarations, not a sandbox.
About
Take software projects from a brief to working code with project onboarding, planning, task management, implementation and handoffs. Includes optional project constitution setup and staged privacy review. Work stays in your linked source repository, with questions handled in chat or Dryft UI.
Capabilities
- Reads files
Linked project source, instructions, briefs, tasks, Git staged changes, proposed commit messages and Dryft workspace context
Understand the project, plan and implement work, and review staged changes for sensitive information.
Leaves your machine: Content read by the agent may be processed by the configured Claude or Codex service.
- Writes files
Authorized linked project source and .dryft/ records; workspace project links and .dryft/state/software-production/ handoffs
Create and update briefs, plans, tasks, implementation files, project preferences and continuity records. Delete selected task records only when explicitly requested.
Leaves your machine: No direct transfer from local writes; external operations are disclosed separately.
- Runs processes
Dryft CLI, Git, bundled Python helpers and authorized project commands
Link projects, validate work, run project checks, inspect staged changes and perform requested development operations.
Leaves your machine: Depends on the authorized command; remote Git operations and project tools may send source, metadata or requests to their configured services.
- Uses a connector
An optional external task system selected and connected by the user
Read, create, update, close or explicitly delete tasks in the chosen authoritative tracker.
Leaves your machine: Task descriptions, status, references and authorized updates go to the selected provider. Not used with the default local Markdown tracker.
- Uses the network
Services required by the linked project and explicitly authorized remote operations
Perform requested development work, dependency retrieval, remote Git operations or external task management.
Leaves your machine: Project-dependent requests and authorized source, task or release data go to the selected services. No independent stack telemetry.
- Other effect
Optional project-local constitution loader and Claude/Codex SessionStart configuration
After authorization, install startup loading of project rules. This setup persists after stack removal.
Leaves your machine: Project rules enter the selected agent’s context and may be processed by its configured service.
Prerequisites
Project registration, workspace context and optional local UI interviews.
Required
Required for staged privacy review and Git-based development operations.
Required for the optional constitution setup and privacy-review helpers. Constitution setup requires POSIX.
Required
Executable hooks
No hooks. Nothing runs on session start or turn completion.
Supported agents
Claude Code and Codex
Release source and checksums
The Dryft CLI downloads this commit from GitHub, never a branch or a moving tag, and refuses the archive unless both digests match. A tag that moves later does not change this record.
Review notes
Reviewed the exact public release archive, ten skills, templates/helpers, prerequisites and data-flow disclosures. Safe unpack, manifest validation and disposable Claude/Codex installation and doctor passed on Linux x86_64/Python 3.12; prior local acceptance retained. No automatic stack hooks or providers. Optional authorized constitution setup creates persistent project-local startup hooks and requires POSIX. External trackers and project-specific tools depend on user configuration. macOS/native Windows remain unverified; this review did not rerun every live-host workflow.
- 0.2.0
- v0.2.0
- b355b0093baec3d616ead522d20e0de02f4542eb77df88c77465f9c3ba63f9ec
- 62a16799bc3a4318a881c66f2f483013f8d098c9504c6054e15887a7c6fcd17b
- v1
Versions
Every approved version, newest first. There are no automatic updates: use dryft stack update dryft-software-production to inspect and approve a newer one.
0.2.0Latest
dryft stack install dryft-software-production --version 0.2.0 --inspectCapabilities
- Reads files
Linked project source, instructions, briefs, tasks, Git staged changes, proposed commit messages and Dryft workspace context
Understand the project, plan and implement work, and review staged changes for sensitive information.
Leaves your machine: Content read by the agent may be processed by the configured Claude or Codex service.
- Writes files
Authorized linked project source and .dryft/ records; workspace project links and .dryft/state/software-production/ handoffs
Create and update briefs, plans, tasks, implementation files, project preferences and continuity records. Delete selected task records only when explicitly requested.
Leaves your machine: No direct transfer from local writes; external operations are disclosed separately.
- Runs processes
Dryft CLI, Git, bundled Python helpers and authorized project commands
Link projects, validate work, run project checks, inspect staged changes and perform requested development operations.
Leaves your machine: Depends on the authorized command; remote Git operations and project tools may send source, metadata or requests to their configured services.
- Uses a connector
An optional external task system selected and connected by the user
Read, create, update, close or explicitly delete tasks in the chosen authoritative tracker.
Leaves your machine: Task descriptions, status, references and authorized updates go to the selected provider. Not used with the default local Markdown tracker.
- Uses the network
Services required by the linked project and explicitly authorized remote operations
Perform requested development work, dependency retrieval, remote Git operations or external task management.
Leaves your machine: Project-dependent requests and authorized source, task or release data go to the selected services. No independent stack telemetry.
- Other effect
Optional project-local constitution loader and Claude/Codex SessionStart configuration
After authorization, install startup loading of project rules. This setup persists after stack removal.
Leaves your machine: Project rules enter the selected agent’s context and may be processed by its configured service.
Prerequisites
Project registration, workspace context and optional local UI interviews.
Required
Required for staged privacy review and Git-based development operations.
Required for the optional constitution setup and privacy-review helpers. Constitution setup requires POSIX.
Required
Executable hooks
No hooks. Nothing runs on session start or turn completion.
Supported agents
Claude Code and Codex