DevWorkWire documentation
Prepared work.
Ready for Jira.
Bring your Epic and Stories in Markdown. Use dwire to validate, preview, and import them from your terminal or through a terminal-capable AI agent.
A local CLI for already refined work. Jira is the current provider.
What you can do today
Preview without Jira writes
Validate your Markdown and inspect create, skip, and unresolved items locally with preview-folder.
Resume with a local record
Imports record created Jira keys beside your Markdown. Keep the resume file so re-runs can skip recorded items; changed uploaded items are not updated.
One CLI for people and agents
Use dwire directly, or let a terminal-capable agent use the same commands through a portable skill. Direct commands support JSON output.
From folder to backlog
Inspect the work before you import it
- Prepare your folder. Keep one Epic in
epic.mdand optional Stories instories.md. - Preview locally. Check validation results and see what will be created or skipped, without writing to Jira.
- Import and keep the state. Review the import preview and confirm in your terminal. Keep
.devworkwire-import.jsonwith the folder for resumable re-runs.
dwire preview-folder ./work-items/my-epic
dwire import-folder ./work-items/my-epic
Direct create commands write immediately. Non-interactive imports require --yes when there is work to create.
Find your next page
Explore the documentation
New to the project? Start with Context and the CLI contract. Contributing? Follow Requirements, Architecture, and Decisions.
Context
The problem, the people, and the project boundaries.
Requirements
Current capabilities, partial features, and future work.
Planning
The draft roadmap, roles, and delivery phases.
Architecture
The CLI, Jira adapter, interfaces, and import state.
Decisions
The reasoning behind the design, including superseded proposals.
Prototype
Interaction references, design direction, and prototype briefs.