work-on-features

Implements unchecked CHANGELOG.md Unreleased features with unit tests and verification.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/ApolonTorq/m365-mail-mirror --skill work-on-features-apolontorq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work-on-features
Source: https://github.com/ApolonTorq/m365-mail-mirror/tree/main/.claude/skills/work-on-features
Command: npx skills add https://github.com/ApolonTorq/m365-mail-mirror --skill work-on-features-apolontorq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually tracking and implementing a backlog of planned features is error-prone and easy to lose track of. This Skill automates the systematic implementation of every incomplete feature listed in the CHANGELOG.md [Unreleased] section, ensuring each one is coded, tested, and marked complete. ## Core Features & Use Cases - Changelog-Driven Workflow: Reads the [Unreleased] section of CHANGELOG.md as the single source of truth and works through unchecked items one at a time. - Test-Enforced Completion: Requires passing dotnet build and dotnet test with xUnit, Moq, and FluentAssertions tests before any feature is marked complete. - Resumable Progress: On re-invocation, resumes from the first unchecked feature, so interrupted sessions continue seamlessly. - Use Case: A maintainer of a .NET project lists ten planned features in CHANGELOG.md, invokes this Skill, and each feature is implemented, tested, and checked off automatically. ## Quick Start Ask the assistant to work on the next incomplete feature from the CHANGELOG.md Unreleased section.

Frequently Asked Questions about work-on-features

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

FAQPage Schema
How do I automate implementing features from a changelog?▼

List planned features as unchecked items in the CHANGELOG.md [Unreleased] section, then invoke this Skill. It reads the changelog, implements each unchecked feature with tests, and marks it complete only after all tests pass.

How does the work-on-features skill track progress?▼

It uses the CHANGELOG.md [Unreleased] section as the single source of truth, checking off items from `- [ ]` to `- [x]` only after implementation and tests succeed. On re-invocation it resumes from the first unchecked item.

What testing frameworks does this workflow require?▼

The workflow uses xUnit for test structure, Moq for mocking dependencies, and FluentAssertions for readable assertions. Tests must be fast, cover happy paths and error cases, and pass via `dotnet test` before completion.

Can I resume feature implementation after an interrupted session?▼

Yes. The Skill always starts by re-reading the CHANGELOG.md [Unreleased] section and continues from the first unchecked feature, so interrupted sessions resume without losing progress.

What happens when a feature implementation gets blocked?▼

The Skill documents the issue, attempts resolution by reading docs or adjusting the approach, and asks the user for guidance if unresolvable. It never marks a blocked feature as complete.