.do
Official@dot-do
Offers structured engineering lifecycle management through test-driven development, project initialization, and systematic code review processes for software teams.
Agent Skills by .do
Showing 13 vetted skills indexed across 2 GitHub repositories.
dot-dotest-driven-development
Enforce a test-first workflow by writing failing tests before code.
dot-dodevelopment-loop
Automate end-to-end software development loops from brainstorming to final approval.
dot-docode-review
Dispatch five specialized subagents to review code and synthesize a unified report.
dot-dobeads
Track TDD phases with Git-native issues using RED, GREEN, and REFACTOR labels.
dot-dobrainstorming
Clarify requirements and structure ideas into modular design sections.
dot-doparade-doctor
Validate Parade project setup components and report health issues.
dot-dodiscover
Transform a feature idea into a detailed specification with complexity assessment.
dot-doevolve
Analyze epic histories to detect new patterns and propose registry updates.
dot-doworkflow-status
Aggregate discovery.db briefs and beads epics into a single workflow view.
dot-dorun-tasks
Orchestrate end-to-end tasks using beads and labeled sub-agents.
dot-doretro
Analyze completed epics to generate structured retrospectives with actionable recommendations.
dot-doapprove-spec
Convert approved specs from discovery.db into beads epics with task breakdowns.
dot-doinit-project
Guide project initialization through a phase-based wizard that writes project.yaml and scaffolds directories.
Frequently Asked Questions About .do
FAQPage SchemaWhat specific engineering tasks does .do enable?▼
.do enables end-to-end software lifecycle management, including project initialization, requirement specification, test-driven development tracking, and automated code review synthesis. It facilitates the transition from initial brainstorming to final retrospective analysis by aggregating project data into structured epics and actionable reports.
Which personas benefit most from .do?▼
Software engineers, technical leads, and project managers benefit from .do. It is designed for teams prioritizing test-first methodologies, rigorous code quality standards, and structured project documentation, helping them maintain consistency across complex development cycles and epic histories.
What are the prerequisites for using .do?▼
Users require a Git-based environment to utilize the issue-labeling features and project directory scaffolding. The system relies on local project.yaml configuration files and discovery.db briefs to maintain state across the development lifecycle, ensuring all tasks remain synchronized with the defined project architecture.