feature-dev

Coordinate end-to-end feature delivery across the Winston monorepo.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/paulmalmquist/Consulting_app --skill feature-dev-paulmalmquist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-dev
Source: https://github.com/paulmalmquist/Consulting_app/tree/main/.skills/feature-dev
Command: npx skills add https://github.com/paulmalmquist/Consulting_app --skill feature-dev-paulmalmquist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating end-to-end feature work across the Winston monorepo is complex and error-prone. This skill reduces coordination overhead by providing a unified workflow that starts from feature description and CLAUDE.md routing, through multi-repo code changes, testing, and deployment considerations.

Core Features & Use Cases

  • End-to-end feature coordination: orchestrates surface routing, code changes, and validation across Winston's monorepo to deliver new features, endpoints, components, or bug fixes.
  • CLAUDE.md-driven routing: reads CLAUDE.md to determine the owning surface (backend, repo-b, repo-c) and routes work to the appropriate service area.
  • Baseline testing and workflow guardrails: enforces running baseline tests before changes, follows the mandated workflow states (orienting, implementing, testing, deploying, verifying), and ensures compliant documentation and verification steps.
  • Use case example: When a user describes a new feature or bug fix, the skill coordinates across all relevant surfaces to implement, test, and prepare the change for deployment.

Quick Start

Describe the feature you want and let this skill coordinate end-to-end delivery in the Winston monorepo.

Frequently Asked Questions about feature-dev

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

FAQPage Schema
How do I coordinate end-to-end feature delivery in a monorepo?

End-to-end feature delivery in a monorepo is coordinated by routing changes across multiple surfaces, enforcing baseline tests, and following defined workflow states from implementation to deployment. This skill automates that orchestration.

What is the workflow for shipping a new feature across backend and repo surfaces?

The workflow for shipping a new feature follows five states: orienting, implementing, testing, deploying, and verifying. It routes code changes across backend and repo surfaces using CLAUDE.md ownership rules.

How do I route code changes to the correct surface in a Winston monorepo?

Routing code changes to the correct surface in a Winston monorepo requires reading CLAUDE.md to determine runtime ownership, which directs work to the appropriate backend, repo-b, or repo-c service area.

Do I need to run baseline tests before implementing a new endpoint or component?

Baseline tests must be run before implementing a new endpoint or component. The workflow enforces running these tests prior to code changes to ensure guardrails are met and validation is traceable.

Can I automate bug fixes and data model changes across multiple repositories?

Bug fixes and data model changes can be automated across multiple repositories by orchestrating surface routing and applying the mandated workflow states. The skill handles multi-repo changes from implementation through live validation.

What's the best way to ensure traceable deployments for monorepo feature work?

Traceable deployments for monorepo feature work are ensured by following the defined workflow states, enforcing baseline tests before changes, and performing live validation during the final verifying stage.