cells-apply

Implement planned tasks into code changes with TDD and scope enforcement.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/PixelDroid19/cells-agents --skill cells-apply
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cells-apply
Source: https://github.com/PixelDroid19/cells-agents/tree/main/skills/cells-apply
Command: npx skills add https://github.com/PixelDroid19/cells-agents --skill cells-apply

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill turns high‑level change proposals, specifications, and design documents into concrete code changes, ensuring disciplined implementation and traceable progress.

Core Features & Use Cases

  • Task Execution: Reads proposals, specs, designs, and task lists to generate code updates.
  • Progress Persistence: Updates Engram or OpenSpec artifacts according to the selected mode, keeping implementation status in sync.
  • Scope & Validation: Enforces strict scope gates, TDD workflows, and optional browser validation for UI changes.

Quick Start

Implement the change named "transfer-button-update" using the cells-apply skill.

Frequently Asked Questions about cells-apply

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement planned tasks into code changes from design documents?

To implement planned tasks into code changes, the skill reads proposals, specifications, and design documents to generate concrete code updates. It ensures disciplined implementation by enforcing strict scope gates and traceable progress synchronization.

How does task automation persist implementation progress across Engram or OpenSpec?

Task automation persists implementation progress by updating Engram or OpenSpec artifacts according to the selected mode. This mechanism keeps implementation status in sync with the defined task lists throughout the code generation process.

Does this code generation workflow support TDD and browser validation for UI changes?

Yes, the code generation workflow supports TDD integration and optional browser validation for UI changes. It enforces strict scope gates to ensure requirements are met without expanding the original task boundaries.

What is the best way to enforce strict scope gates during task execution?

The best way to enforce strict scope gates during task execution is using mode-specific persistence like Engram or OpenSpec. This ensures generated code updates strictly align with the original proposals, specifications, and design documents.

Can I use this for task automation without predefined task lists and specs?

No, this task automation requires predefined task lists, proposals, specs, and designs as input. It relies on these structured planning documents to generate accurate code changes and maintain traceable implementation progress.