comet-open

Name: comet-open
Availability: InStock
Author: zhentingwu-wzt

Standardize project initiation with structured requirement gathering and artifact generation.

6|Updated May 25, 2026

Search Tags:#workflow #planning #development #architecture #requirements #comet

Ready to run

npx skills add https://github.com/zhentingWu-wzt/wgenty-code --skill comet-open-zhentingwu-wzt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: comet-open
Source: https://github.com/zhentingWu-wzt/wgenty-code/tree/main/.wgenty-code/skills/comet-open
Command: npx skills add https://github.com/zhentingWu-wzt/wgenty-code --skill comet-open-zhentingwu-wzt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of unstructured project initiation by enforcing a rigorous, multi-stage workflow for defining, clarifying, and planning new development changes.

Core Features & Use Cases

Requirement Clarification: Guides users through a structured exploration of goals, non-goals, and acceptance criteria to prevent scope creep.
Change Structuring: Automatically generates standardized proposal, design, and task documentation to ensure architectural alignment.
Use Case: When starting a new feature or refactor, use this Skill to ensure the project is fully scoped, dependencies are identified, and a clear execution plan is established before any code is written.

Quick Start

Use the comet-open skill to initialize a new development change for the upcoming authentication module upgrade.

Frequently Asked Questions about comet-open

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

FAQPage Schema

How do I structure project initiation for a complex software development change?▼

To structure project initiation for a complex software development change, enforce a multi-stage workflow that defines goals, clarifies requirements, and generates standardized proposal, design, and task documentation. This ensures architectural consistency and project scope alignment before implementation begins.

What is the best way to prevent scope creep when planning new software features?▼

The best way to prevent scope creep when planning new software features is through structured requirement gathering. By guiding a structured exploration of goals, non-goals, and acceptance criteria, you establish clear project boundaries and ensure architectural alignment before coding starts.

How do I generate design and task documentation before starting a refactor?▼

To generate design and task documentation before starting a refactor, use a structured planning workflow that automatically creates standardized artifacts. This process enforces multi-stage validation to identify dependencies and establish a clear execution plan for the technical changes.

Do I need to define acceptance criteria before generating project planning artifacts?▼

Yes, you need to define acceptance criteria before generating project planning artifacts. Clarifying goals, non-goals, and acceptance criteria is a required multi-stage validation step to ensure architectural consistency and prevent scope creep before any implementation begins.

When should I use a structured workflow for software architecture planning?▼

You should use a structured workflow for software architecture planning when starting a new feature or complex refactor. It ensures the project is fully scoped, dependencies are identified, and a clear execution plan is established through multi-stage validation before any code is written.

Why does unstructured project initiation cause problems in software development?▼

Unstructured project initiation causes problems in software development because it lacks rigorous requirement gathering and scope clarification. Without enforcing a multi-stage validation process to generate design and task documentation, projects suffer from scope creep, unidentified dependencies, and architectural inconsistencies.