Tdd workflows tdd green

Skill sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/tdd-workflows-tdd-green

AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 1,987+ agentic skills. Includes CLI, local MCP, catalog, plugins, and Workbench.

Install

npx -y skills add sickn33/agentic-awesome-skills --skill tdd-workflows-tdd-green

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Implement the minimal code needed to make failing tests pass in the TDD green phase.

SKILL.md

2.2 KB, as published. Nobody here has run it

Green Phase: Simple function

def product_list(request): products = Product.objects.all() return JsonResponse({'products': list(products.values())})

Refactor: Class-based view

class ProductListView(View): def get(self, request): products = Product.objects.all() return JsonResponse({'products': list(products.values())})

Refactor: Generic view

class ProductListView(ListView): model = Product context_object_name = 'products'


### Express Patterns

**Inline → Middleware → Service Layer:**
```javascript
// Green Phase: Inline logic
app.post('/api/users', (req, res) => {
  const user = { id: Date.now(), ...req.body };
  users.push(user);
  res.json(user);
});

// Refactor: Extract middleware
app.post('/api/users', validateUser, (req, res) => {
  const user = userService.create(req.body);
  res.json(user);
});

// Refactor: Full layering
app.post('/api/users',
  validateUser,
  asyncHandler(userController.create)
);

Use this skill when

Moving from red to green in a TDD cycle
Implementing minimal behavior to satisfy tests
You want to keep implementation intentionally simple

Do not use this skill when

You are refactoring for design or performance
Tests are already passing and you need new requirements
You need a full architectural redesign

Instructions

Review failing tests and identify the smallest fix.
Implement the minimal change to pass the next test.
Run tests after each change to confirm progress.
Record shortcuts or debt for the refactor phase.

Safety

Avoid bypassing tests to make them pass.
Keep changes scoped to the failing behavior only.

Resources

resources/implementation-playbook.md for detailed patterns and examples.

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.