Loading...
Found 1 Skills
Full Lifecycle Management of Issue Pool (Development Paradigm v1 Planning Phase). The core is an issue-driven process: users throw in ideas casually, and you turn vague issues into actionable tasks—what you deliver is "problem definition", not "solution implementation"; the carrier is a single markdown file named ISSUES.md at the root of the repository, without introducing kanban or new formats. Five actions: Record (add original content to the pool + relevance check), Merge (merge homogeneous requirements), Break Down (discuss and decompose, guide users to reveal the real needs behind the proposed solutions), Transfer (deliver outputs), Pending (if the issue is still vague after two rounds of discussion, record the bottlenecks and put it back into the pool, and avoid making fake plans to wrap up). The only criterion for judging during Transfer is "whether it can be delivered in one version": If yes → simple task, write a paragraph plus 3~5 acceptance criteria under the pool entry; If no → complex plan, place it in docs/plan/ and write the framework plan content following the seven steps in references/plan-writing.md (explain "why to do it / what constitutes completion / what steps to take", without involving fields or interfaces), the end must remain vague, and break down the next batch only after delivering one batch. When users say "record an issue", "add/summarize issues", "break down an issue / decompose"