| verblock | 24 Feb 2026:v0.4: Matthew Sinclair - Updated for Intent v2.5.0 |
|---|---|
| intent_version | 2.5.0 |
This document tracks features, files, and functionality that have been deprecated in Intent (formerly STP).
The Backlog.md integration and all associated commands (intent bl, intent task, intent migrate) have been removed.
Backlog.md task management added complexity without sufficient value. Steel threads and their associated task files (tasks.md, done.md) provide adequate tracking for Intent's workflow. Removing the Backlog integration simplifies the codebase and reduces maintenance burden.
Users who were using Backlog.md should:
- Move any active tasks into steel thread
tasks.mdfiles - Archive historical task data if needed
- Remove
Backlog.mdfrom project roots
- The
intent blcommand has been removed - The
intent taskcommand has been removed - The
intent migratecommand has been removed - Associated test files (
bl_commands.bats,task_commands.bats,migration.bats) have been removed - Documentation updated to remove Backlog references
Intent version 2.5.0
The stp/prj/journal.md file and associated functionality.
With the integration of Backlog.md for task management, the journal.md file became redundant. Backlog provides:
- Better structured task tracking with metadata (status, priority, dependencies)
- Automatic linking to steel threads
- More flexible historical tracking through task history
- Integration with modern development workflows
Users who were using journal.md for historical tracking should:
- Use
stp bl listto view task history - Use steel thread documents for high-level context and decisions
- Use Backlog task descriptions for detailed implementation notes
The original journal.md file has been archived at stp/prj/archive/journal-deprecated.md with a deprecation notice.
- The
stp initcommand no longer creates journal.md - Documentation has been updated to reference Backlog for historical tracking
- The journal.md template has been removed from
_templ/prj/
STP version 1.0.0
The entire STP (Steel Thread Process) command and naming convention has been deprecated in favour of Intent.
The name "Intent" better reflects the tool's core purpose of capturing and preserving the intention behind software development decisions. The rebrand includes:
- Better alignment with the tool's philosophy
- Clearer separation between tool and methodology
- Improved directory structure with flattened hierarchy
- Modern JSON-based configuration system
Users migrating from STP to Intent should:
- Run
intent upgradeto automatically migrate existing projects - Update PATH to point to the new bin/ directory
- Use
intentcommand instead ofstp(symlink provided for compatibility) - Update any scripts or documentation referencing
stpcommands
stp→intent(all subcommands remain the same)stp init→intent initstp st→intent ststp bl→intent blstp task→intent taskstp status→intent statusstp migrate→intent migratestp upgrade→intent upgrade
stp/prj/st/→intent/st/stp/prj/wip.md→intent/wip.mdstp/eng/→intent/eng/stp/usr/→intent/usr/stp/bin/→bin/(moved to top level)
- YAML format → JSON format
.stp/config.yml→.intent/config.json- No global config →
~/.config/intent/config.json(XDG standard)
- Original STP executables remain in the repository for reference
- Migration is handled automatically by
intent upgrade - Backwards compatibility maintained through symlinks
- All new projects should use Intent commands and structure
- Existing projects can continue using
stpvia compatibility symlink - Documentation has been updated to use Intent terminology
- Repository renamed from
stptointent
Intent version 2.1.0