Structured project evolution workflow: assess current state, generate upgrade ideas, build roadmaps, and execute via Gitea or GitHub issues and PRs. Use when user asks "what should I do next?", "suggest improvements", "plan next steps", "assess current state", "create upgrade plan", "what can we improve?", "help me plan the next version", "nên làm gì tiếp?", "đề xuất cải tiến", or needs guidance on project direction and incremental improvement.
Guide users from current state assessment through idea generation, planning, and execution.
Before starting, check if prior state exists:
docs/states/current.md exists → ask user: "Tiếp tục từ lần trước hay đánh giá lại?"docs/plans/roadmap.md exists → show current roadmap status and ask which step to resumeAnalyze the project by reading codebase, git log --oneline -20, test coverage, CI config, and dependencies.
Write findings to docs/states/current.md:
# Project State — {date}
## Overview
{1-2 sentences: what the project does, current maturity}
## Strengths
- {concrete strength with evidence}
## Gaps
- {concrete gap with impact}
## Technical Debt
- {specific debt items}
## Metrics
- Files: {count} | Tests: {count} | Dependencies: {count}
- CI/CD: {status} | Last commit: {date}
After writing docs/states/current.md, proceed directly to Step 1 without asking.
Propose 5 practical ideas ranked by impact and feasibility.
Write to docs/ideas/upgrade-{yyyy-mm-dd}.md:
# Upgrade Ideas — {date}
Based on: docs/states/current.md
| # | Idea | Impact | Effort | Description |
|---|------|--------|--------|-------------|
| 1 | {title} | High | Low | {1-2 sentences} |
| 2 | ... | ... | ... | ... |
## Chi tiết
### 1. {title}
{2-3 câu giải thích: vấn đề hiện tại là gì, ý tưởng giải quyết như thế nào, kết quả kỳ vọng}
### 2. {title}
...
Present to user. Do not proceed until user selects which ideas to pursue.
Refine selected ideas into concrete upgrade scope with user.
Write to docs/plans/roadmap.md:
# Roadmap
## Version {x.y.z} — {codename}
- **Goal**: {one-line summary}
- **Scope**: {selected ideas}
- **Out of scope**: {excluded items}
- **Dependencies**: {blockers}
Review roadmap with user:
docs/plans/roadmap.md with status markers: [ ] pending, [x] doneDetect platform (see Platform Detection below), then for each roadmap item:
Issue template:
## Bối cảnh
{Tại sao issue này cần thiết? Liên kết với roadmap item nào?}
Ref: docs/plans/roadmap.md#{version}
## Mô tả
{Mô tả chi tiết công việc cần làm, bao gồm cả hướng tiếp cận đề xuất}
## Phạm vi thay đổi
- Files/modules bị ảnh hưởng: {danh sách file hoặc module}
- Dependencies mới (nếu có): {packages, libraries}
## Acceptance Criteria
- [ ] {criterion 1}
- [ ] {criterion 2}
- [ ] {criterion 3}
## Ghi chú kỹ thuật
- **Ảnh hưởng**: {các phần khác của hệ thống bị ảnh hưởng, nếu có}
- **Rủi ro**: {rủi ro tiềm ẩn hoặc "Không có rủi ro đặc biệt"}
- **Ước lượng**: S / M / L
## Labels
{feature, bugfix, refactor, docs, test — chọn phù hợp}
For independent work items, create separate branches and PRs.
Branch naming: feat/{issue-number}-{short-description}
Detect which platform to use for issues/PRs:
git remote get-url origingit.microai.club or other Gitea host → use /gitea skillgithub.com → use gh CLI or GitHub MCP toolsdocs/issues/ as fallbackSee references/platforms.md for platform-specific commands.
/gitea skill (plugin gitea-skill). If not installed, fallback to markdown output in docs/issues/gh CLI installed and authenticatedAfter completing each step, automatically trigger the health-check skill with scoped dimensions:
| After Step | Health-check dimensions |
|---|---|
| Step 0 | Consistency, Completeness |
| Step 1 | Alignment |
| Step 2 | Alignment, Consistency |
| Step 3 | Consistency, Completeness |
| Step 4 | Consistency, Completeness, Risks |
| Step 5 | All 6 dimensions (full check) |
Do not ask user permission for health-check — it runs automatically. Report results inline before proceeding to the next step.