buiducnhat/co-drew
6 skills6 installs312 starsGitHub
Install
npx skills add https://github.com/buiducnhat/co-drewSkills in this repo
1Brainstormbrainstorm converts ambiguous or high-risk ideas into a clear, reviewable design brief through structured dialogue. A developer uses it when requirements are unclear or multiple approaches are possible, before planning or coding. It clarifies requirements, explores 2-5 approaches with trade-offs, presents the design incrementally, and hands off to write-plan.1installs2Docsdocs creates and maintains project documentation in a docs/ folder with a consistent, lightweight structure. A developer uses it to initialize docs for a new project or sync existing docs to the current codebase. It generates architecture, codebase, code-standard, and product-pdr sections plus a SUMMARY.md entry point and keeps README aligned.1installs3Execute Planexecute-plan carries out a pre-approved implementation plan with strict adherence to scope, sequence, and verification. A developer uses it after write-plan produces a plan, to implement each phase, run phase verification, and record progress in the living SUMMARY.md. It supports batch and interactive modes and produces an execution report at the end.1installs4Quick Implementquick-implement makes small features or bug fixes directly, with strict scope control and verification. A developer uses it when a task is narrow, has clear acceptance criteria, and can be done safely without a formal multi-phase plan. It enforces a scope gate and hard-stop escalation criteria, handing off to write-plan when complexity or risk grows.1installs5Visualizevisualize creates source-adjacent HTML visualizations from repository documentation, markdown files, and standardized plan folders. A developer uses it to turn docs, plans, and process flows into readable maps, timelines, flows, and Mermaid diagrams. It is documentation-focused, uses fixed templates and a shared theme, and never invents facts or metrics.1installs6Write Planwrite-plan creates detailed, execution-ready implementation plans for complex or high-risk changes without writing code. A developer uses it before large refactors, migrations, or multi-hour changes to produce a phased plan with verification commands and observable acceptance criteria. The plan is saved under docs/plans and handed off to execute-plan so a fresh agent can carry it out after /clear.1installs