Skip to content

Latest commit

 

History

History
74 lines (53 loc) · 2.44 KB

File metadata and controls

74 lines (53 loc) · 2.44 KB

Mujeeb Dev Toolkit

A personal collection of OpenCode tools, skills, commands, and plugins for iterative development workflows.

Overview

This toolkit provides:

  • Iterative loop workflows - PRD generation, unit test coverage, E2E test planning
  • Session memory - Context injection from past sessions via qmd
  • Git safety - Blocks destructive git commands
  • Task management - Uses OpenCode's native todowrite/todoread for task tracking
  • Code quality - Deslop tool to remove AI-generated code cruft

Key Workflows

PRD-Based Development (/prd)

A 4-phase workflow for generating comprehensive Product Requirement Documents:

  1. Input classification
  2. Interview + parallel research agents
  3. Spec writing to plans/<feature>/spec.md
  4. Task handoff (creates todos from stories)

Unit Test Loop (/ut)

2-phase workflow for test coverage improvement:

  1. Coverage analysis and gap identification
  2. Task creation for each gap (via todowrite)

E2E Test Loop (/e2e)

2-phase workflow for end-to-end test planning:

  1. Flow analysis and critical path identification
  2. Task creation per flow (via todowrite)

Task Completion (/complete)

Runs code reviewers, addresses findings, commits changes, marks task complete.

External Dependencies

Some features require external tools:

  • qmd - Session memory search (brew install qmd or cargo install qmd)

Conventions

  • Specs go in plans/<feature>/spec.md
  • Loop state files: .opencode/{prd,ut,e2e}-loop-*.local.md
  • Atomic commits per task
  • All tests/lint/types must pass before completing tasks

Code Quality Standards

  • Production quality always
  • Pre-commit reviews required (code-simplifier)
  • Verify work with tests before marking complete
  • Result must include concrete verification, not vague claims

Known Issues

todowrite/question tools broken with array parameters (OpenCode Issue #7512)

Tools with array/object parameters (todowrite, question, etc.) fail with Zod validation errors:

Error: expected array, received string

Root cause: LLMs serialize array parameters as JSON strings ("[{...}]") instead of actual arrays ([{...}]).

Status: Fix in progress (PR #7513), not yet merged.

Workaround: Track tasks manually in conversation or use markdown files until fix is merged.

Affected tools:

  • todowrite (todos array)
  • question (questions array)
  • browser_fill_form (fields array)
  • Any MCP tool with array/object parameters