opencode-feature-workflow
v0.4.1
Published
Feature lifecycle management plugin for OpenCode
Maintainers
Readme
opencode-feature-workflow
Feature lifecycle management plugin for OpenCode. Tracks features from idea to completion with structured workflows, specialized agents, and quality gates.
Install
One command sets everything up:
bunx opencode-feature-workflow setup --projectThis does two things:
- Adds
opencode-feature-workflowto youropencode.jsonplugin array (OpenCode auto-installs npm plugins at startup) - Copies command files to
.opencode/commands/for slash command access
Restart OpenCode after running setup.
Global install
To install globally (available in all projects):
bunx opencode-feature-workflow setupInitialize the workflow structure
After installing, run /feature-init in OpenCode to create the docs/features/ directory and initial DASHBOARD.md.
Commands
| Command | Description |
|---------|-------------|
| /feature-capture | Add a new feature to the backlog |
| /feature-plan [id] | Start implementing a feature with planning workflow |
| /feature-ship [id] | Complete a feature with quality gates |
| /feature-status | Show the feature dashboard |
| /feature-init | Initialize the feature workflow structure |
Feature Lifecycle
Features are tracked by file presence in docs/features/[id]/:
| Files Present | Status |
|---------------|--------|
| idea.md only | Backlog |
| idea.md + plan.md | In Progress |
| idea.md + plan.md + shipped.md | Completed |
docs/features/
├── DASHBOARD.md # Auto-generated, read-only
├── my-feature/
│ ├── idea.md # Problem statement + metadata
│ ├── plan.md # Implementation plan
│ └── shipped.md # Completion notes
└── another-feature/
└── idea.mdHow It Works
Capture
/feature-capture asks for the problem statement, auto-generates a name and ID, suggests smart defaults (type, priority, effort, impact), and creates docs/features/[id]/idea.md.
Plan
/feature-plan dispatches specialized agents based on feature type:
@project-managerfor requirements analysis@api-designer,@frontend-architect,@integration-designerfor architecture- Creates
plan.mdwith implementation steps
Ship
/feature-ship runs quality gates before marking complete:
@security-reviewerfor security audit@qa-engineerfor QA validation- Creates
shipped.mdon passing
Automatic Behaviors
The plugin automatically:
- Generates
DASHBOARD.mdon any feature file change - Blocks direct writes to DASHBOARD.md
- Updates session title when working on features
- Shows toast notifications for status changes
Agents
| Agent | Purpose |
|-------|---------|
| @project-manager | Requirements analysis and user stories |
| @security-reviewer | Security vulnerability detection |
| @qa-engineer | Test coverage and acceptance criteria |
| @api-designer | API/GraphQL design |
| @frontend-architect | React component architecture |
| @integration-designer | Frontend-backend integration |
| @system-designer | High-level architecture |
| @ux-optimizer | UX optimization |
| @code-archaeologist | Reverse-engineer legacy code |
| @test-generator | TDD - write tests before implementation |
| @documentation-agent | Documentation maintenance |
| @runtime-auditor | Runtime auditing |
Plugin Architecture
| Mechanism | How it works |
|-----------|-------------|
| Tools | Registered in src/index.ts, loaded via opencode.json plugin array |
| Skills | SKILL.md files auto-discovered from the npm package |
| Commands | Copied to .opencode/commands/ by the setup script |
| Hooks | File write detection for dashboard generation and status tracking |
Development
bun install
bun run build
bun testLicense
MIT
