Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
TDD-first development workflow with structured planning, task tracking, and PR-based code review. Use when building software projects that require clarificat...
TDD-first development workflow with structured planning, task tracking, and PR-based code review. Use when building software projects that require clarificat...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
A structured development workflow enforcing quality through planning, TDD, and code review.
Clarify โ Plan โ Approve โ Implement (TDD) โ PR โ Review โ Merge โ Next Task
Before any implementation, ask questions to clarify: Business requirements and goals UI/UX flow expectations Architecture decisions Technical constraints Ambiguous requirements Do not proceed until requirements are clear.
Present a detailed plan with task breakdown Keep tasks small and focused Wait for explicit approval before starting No implementation without approval
Set up Trello board (or similar) with columns: ๐ Backlog ๐ To Do ๐จ In Progress ๐ Review โ Done All tasks must be tracked on the board.
For each task: Move card to "In Progress" Write tests first (TDD): Define expected behavior in tests Run tests (should fail) Implement the feature Run tests (should pass) Commit after task completion Tests may be skipped only with explicit approval
Rules: Never push directly to main Never change the default branch โ main must always remain default Create feature branches for each task After task completion: Open PR from task branch โ main Include Trello task link in PR description Move card to "Review" Notify Reviewer with both Trello link and PR link
When CR comments arrive: Move task back to "In Progress" Address all review comments Push fixes Notify Reviewer to re-review (include both links) Repeat until approved.
Only pick the next task after current PR is merged Move completed card to "Done" Then proceed to next task from "To Do"
Backlog โ To Do โ In Progress โ Review โ Done โ โ โโโโ CR โโโโโโ
For new projects: Create repository with initial README Push to remote Then begin implementation tasks
Quality over speed โ TDD catches bugs early Small tasks โ easier to review and merge Clear communication โ always notify reviewers No shortcuts โ follow the process every time
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.