dev-task

What This Skill Does

The dev-task skill is a sophisticated project management and version control agent designed specifically for OpenClaw developers. It enforces a strict, disciplined workflow for software development lifecycles. By mandating a structured hierarchy for documentation and source code, it ensures that every iteration of a project is traceable, reproducible, and safely archived. The skill acts as a gatekeeper, preventing 'code drift' by requiring explicit version confirmation before tasks begin and mandatory archival procedures upon completion.

Installation

You can install this skill directly into your OpenClaw environment using the following command: clawhub install openclaw/skills/skills/cwyhkyochen-a11y/dev-task

Use Cases

• Professional Software Development: Managing complex codebases where history and rollback capabilities are critical for stability.
• Team Coordination: Ensuring that all developers follow a unified directory structure for requirements and deployment documentation.
• Strict Release Management: Automating the transition process from active development to final version archiving to prevent loss of milestone state.
• Documentation Compliance: Forcing teams to update CHANGELOG.md, REQUIREMENTS.md, and DEPLOY.md before a release can be finalized.

Example Prompts

1. "I want to start a new feature for the user authentication module. Let's initialize version v1.2.0 for this."
2. "I have finished the development for the current release. Can you help me walk through the封版 (closing) process and verify all my documentation is ready?"
3. "Check the current project status and let me know if there are any unarchived versions from our previous development sessions."

Tips & Limitations

• Iron Discipline: The skill is designed to be restrictive. If you attempt to start a new version without archiving the previous one, the agent will block your request. Always finish your archival checklist before starting a new sprint.
• Directory Hygiene: Strictly adhere to the /versions/ directory convention. Manually moving files outside this structure may break the automated script's ability to locate your previous work.
• Documentation Priority: Treat CHANGELOG, REQUIREMENTS, and DEPLOY files as living documents. The skill relies on their existence and consistent formatting to execute successful archival procedures.