code-dev-workflow
SolidNear code_dev harness — Explore, Read, Author phases with outline-first context discipline.
Install
Quality Score: 78/100
Skill Content
Details
- Author
- opencue
- Repository
- opencue/cuecards
- Created
- 2 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
developer-workflow
Use when the user is writing, reviewing, debugging, testing, or refactoring code, or wants help with commits and pull requests. Emphasizes reading existing code first, verifying changes, and never inventing APIs.
task-code
task-code workflow v3 — Stage ③.b 子任务编码 sub-workflow (karpathy 4 心法 always-on + mattpocock conditional route + planning-with-files progress.md update)。 2-phase composition: 01-code (karpathy 心法 + improve-arch 周期审查 / diagnose bug conditional invokes_tools) → 02-progress (Claude Code plugin /plan 更新 progress.md 跨 session 进度同步)。 schema_version: harnessed.workflow.v3 with disciplines_applied [6] + tools_available [improve-codebase-architecture, diagnose, planning-with-files]. Triggered by harnessed CLI `harnessed task-code --task <text>` or slash command `/task-code` after `harnessed setup`.
autonomous-workflow
Execute development workflows through Explore-Plan-Code-Verify phases with task-driven tracking, Tier 1/2/3 action classification, decision journaling, and bounded debug loops. Use when executing any development workflow autonomously or orchestrating multi-step implementation tasks. This skill MUST be consulted because skipping phases causes rework, and unbounded verification loops cause agents to loop forever on unsolvable problems.