avito-scraper-implementation

Implement projects end-to-end from requirements, design, and tasks documents.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/Stepan2222000/local-validator --skill avito-scraper-implementation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: avito-scraper-implementation
Source: https://github.com/Stepan2222000/local-validator/tree/main/.claude/skills/task_implement
Command: npx skills add https://github.com/Stepan2222000/local-validator --skill avito-scraper-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures end-to-end project delivery exactly according to provided specifications, preventing scope drift and misinterpretation.

Core Features & Use Cases

  • Enforces adherence to requirements, design, and task docs to guide deterministic development.
  • Integrates a structured, evidence-driven workflow with tests, commits, and subagent verification.
  • Use Case: When starting a new project, activate this Skill to align the team on specs and trigger a compliant implementation cycle.

Quick Start

Follow the specifications in requirements.md, design.md, and tasks.md to deliver a complete project implementation with all tests and verifications.

Frequently Asked Questions about avito-scraper-implementation

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

FAQPage Schema
How do I automate project implementation to strictly follow provided specifications?

Automated project implementation follows provided specification documents like requirements.md, design.md, and tasks.md to guide deterministic development with test-driven execution and Git-based verification. This ensures traceable commits across multiple tasks and prevents scope drift.

What is documentation-driven development and how does it ensure test coverage?

Documentation-driven development aligns software delivery with written requirements and design docs by enforcing test-driven development alongside subagent verification. This process validates every specification requirement through automated integration testing before committing code.

Does this automated implementation workflow require specific specification file formats?

Yes, the automated implementation workflow requires specific specification file formats, specifically requirements.md, design.md, and tasks.md. Providing these structured documents ensures deterministic task execution and subagent verification function correctly to deliver the complete project.

How do I set up a Git workflow with automated verification for multi-task software projects?

Setting up a Git workflow with automated verification involves executing deterministic tasks from specification docs and committing traceable code only after passing integration testing and subagent verification. This structured approach maintains quality assurance across the entire project implementation cycle.

What is the best way to prevent scope drift when implementing from design docs?

Preventing scope drift during implementation requires strict adherence to design docs through evidence-driven workflows with automated subagent verification. Enforcing test-driven development against the original specifications guarantees project delivery exactly matches the documented requirements without misinterpretation.