Technical plans often drift from product intent or the current codebase. This skill researches repository structure and turns constraints into an actionable TECH.md implementation plan.

Spec-triggered documentation created drafts for features that had not shipped. This retired skill explains the failure and directs users to release-gated alternatives.

Volcengine VoiceChat integrations involve changing APIs, models, audio settings, and runtime stages. This skill provides safe configuration guidance, official documentation routing, and evidence-based troubleshooting.

Ponytail users need a clear reference for modes, commands, and configuration. This skill displays that reference once without changing modes or saving state.

Ambiguous requirements create conflicting implementations and unverifiable reviews. This skill guides linked specifications, risk assessments, and verification strategies through explicit human approval.

Vague architecture leaves teams with incompatible interfaces and undocumented decisions. This skill structures architecture, decisions, contracts, and component designs for human review before specification.

Teams often declare work complete without proving every requirement, path, review, and gap. This skill creates a traceable chain from intent to evidence and a defensible delivery decision.

OpenSpec tasks and archive states do not prove evidence-backed completion. This skill maps requirements, acceptance items, journeys, and gates into an auditable RVTF closure process.

BMAD work can lose traceability between requirements, reviews, tests, and closure decisions. This skill maps BMAD artifacts to RVTF records while preserving host ownership, evidence quality, and review boundaries.

Project stack documentation often becomes incomplete after dependency changes. This skill detects supported technologies and updates .specsfy/STACK.md while preserving human-authored content.

Structural changes can leave project documentation incomplete or contradictory. This skill identifies affected documents and keeps durable decisions aligned with the code.

Stale context files mislead agents and increase maintenance risk. Gardener verifies documentation against code, repairs references, and keeps risk baselines controlled.

Coding agents lose accuracy when repository guidance is missing or outdated. This skill creates reviewed context files, confidence labels, and risk boundaries with human approval.

Understanding an unfamiliar Convex application requires connecting schemas, functions, authentication, and integrations. This skill produces a structured, source-grounded architecture map without modifying the application.

Website teams need a careful way to explore emerging discovery files and structured data. This skill previews candidate artifacts and keeps approval with the user before writing changes.

Long project instructions can hide important guidance and verification steps. This skill restructures them into concise root guidance and focused rule files.

Documentation updates often land in the wrong file or duplicate existing information. This skill directs the assistant to the owning documentation layer and keeps project guidance consistent.

API documentation can drift from the schemas and routes that define actual behavior. This skill guides updates from the owning source and keeps generated artifacts out of manual edits.

Architecture decisions often remain scattered across requirements, discussions, and diagrams. This skill organizes them into consistent Markdown documents for implementation and review.

Das Erstellen einer ausgereiften Awesome-Liste erfordert eine sorgfältige Struktur, Beitragsregeln und Verifizierungsschritte. Diese Skill generiert aus einem Thema und Startressourcen ein fokussiertes Repository-Scaffold.