project-evolution

Track features, architectural decisions, technical debt, and release notes for software projects.

Updated Aug 27, 2026

Search Tags:#project management #technical debt #software documentation #feature lifecycle #project evolution

Ready to run

npx skills add https://github.com/PAISHU-AI/PAI-zong-NB --skill project-evolution

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-evolution
Source: https://github.com/PAISHU-AI/PAI-zong-NB/tree/main/skills/36-project-evolution
Command: npx skills add https://github.com/PAISHU-AI/PAI-zong-NB --skill project-evolution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining a project's evolution over time, ensuring that all changes, decisions, and technical details are documented and accessible.

Core Features & Use Cases

Feature Lifecycle Management: Track features from planning to implementation and beyond.
Decision Records: Document and manage Architecture Decision Records (ADR) for project changes.
Technical Debt Management: Keep track of technical debt and prioritize cleanup efforts.
Documentation Management: Organize project documentation, including roadmaps, change logs, and technical debt records.
Use Case: For a software project, use this Skill to document the feature lifecycle, architectural changes, and technical debt associated with a recent release.

Quick Start

Run the 'project-evolution' skill to create a new project evolution document for your project.

Frequently Asked Questions about project-evolution

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

FAQPage Schema

How do I track technical debt and architectural decisions in a software project?▼

You track technical debt and architectural decisions by maintaining Architecture Decision Records (ADR) and debt logs. This manages project evolution by documenting structural changes and prioritizing cleanup efforts for future reference.

What is the best way to document feature lifecycle from planning to release?▼

Documenting feature lifecycle involves tracking features from planning to release and beyond. This records project evolution by capturing upgrade history and change logs, ensuring all modifications remain accessible for software maintenance.

When do I need to maintain project evolution documentation for software upgrades?▼

Maintain project evolution documentation when adding features, planning upgrades, or changing software architecture. This organizes release notes and known issues, ensuring durable development process records remain accessible during major project modifications.

Does this feature lifecycle management approach work for tracking known issues and refactor candidates?▼

Yes, feature lifecycle management tracks known issues and refactor candidates. It manages project evolution by recording architectural decisions, technical debt, and upgrade history, organizing software documentation for ongoing maintenance.

How to create a new project evolution document for an existing codebase?▼

To create a new project evolution document, run the project-evolution skill. It initializes comprehensive tracking for architectural decisions, technical debt, and release notes, structuring the complete history of your existing software project.