feat-dev

Automate end-to-end feature development in glm-code with structured phases.

Updated May 15, 2026
One-click install
npx skills add https://github.com/qazz92/glm-code --skill feat-dev-qazz92
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feat-dev
Source: https://github.com/qazz92/glm-code/tree/main/.glm/skills/feat-dev
Command: npx skills add https://github.com/qazz92/glm-code --skill feat-dev-qazz92

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the complexity of implementing non-trivial features in glm-code by providing a structured workflow that covers requirements, design, testing, and iteration.

Core Features & Use Cases

  • End-to-End Workflow: Covers investigation, design, E2E test planning, dry-run, implementation, verification, code review, and iteration.
  • Investigation: Helps understand the current behavior and desired changes.
  • Design Documentation: Facilitates the creation of a detailed design doc.
  • Test Planning: Utilizes the e2e-testing skill for comprehensive test planning.
  • Implementation: Guides the implementation phase with best practices.
  • Verification: Ensures that the feature works as intended through testing.
  • Code Review: Streamlines the code review process with a structured approach.

Quick Start

Use the feat-dev skill to initiate the feature development workflow for a new glm-code feature.

Frequently Asked Questions about feat-dev

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

FAQPage Schema
How do I streamline feature development workflow in glm-code?

Streamline feature development in glm-code by using an automated end-to-end workflow that covers investigation, design, E2E test planning, dry-run, implementation, verification, and code review. This structured approach reduces errors and enhances productivity for complex feature implementations.

What is the best way to plan end-to-end tests for a new feature?

Plan end-to-end tests for new features by utilizing a dedicated e2e-testing skill within the broader feature development workflow. This ensures comprehensive test planning and verification before moving into the actual implementation phase.

How do I structure the design documentation for complex feature implementations?

Structure design documentation for complex feature implementations by following a guided workflow that transitions from initial behavior investigation directly into creating a detailed design doc. This ensures all desired changes are captured accurately before coding begins.

Does the feature development workflow include a dry-run phase?

Yes, the feature development workflow includes a dry-run phase. It operates alongside investigation, E2E test planning, implementation, verification, and code review to ensure features work as intended before final iteration.

How do I conduct a structured code review after feature implementation?

Conduct a structured code review after feature implementation by using an automated workflow that verifies the feature works as intended through testing before streamlining the review process. This reduces the risk of errors in complex implementations.

When do I need an automated workflow for software engineering tasks?

You need an automated workflow for software engineering tasks when implementing non-trivial features that require structured guidance across requirements, design, testing, and iteration. This prevents errors that often occur in unstructured, complex feature implementations.