Loading...
Loading...
Found 7 Skills
Archive completed plans from plans/active/ to plans/completed/, supplement verification results and completion time. Suitable for calling after implementation is finished.
Scaffolds new projects with README.md, AGENTS.md, and CI/CD (GitLab CI, GitHub Actions). Handles project type (generic / Flask backend / React frontend / Taro miniapp), tech stack, coding standards, quality level, and SDD (OpenSpec, SpecKit, GSD). All init flows (Flask, React, Taro) and conventions (backend-python-cicd, frontend-codegen, flask-backend-codegen, QA/testing, agent-roles/subagents) are built-in; no separate skills. Docs default to Chinese. Use when creating a project, initializing a repo, or setting up CI/CD/SDD.
When the boundaries are clear, directly implement code, tests and necessary documentation, and complete the implementation and closure with minimal interruptions
Used when you need to perform Discover (reverse engineering) on legacy projects with existing code, consolidate repository facts into `.aisdlc/project/`, and you find that AI or teams frequently guess entry points and boundaries, have duplicate writing of indexes and details, or lack evidence chains leading to repeated rework.
Search Sourcegraph-indexed codebases for patterns, examples, and system understanding. Triggers on implementation questions, debugging, or "how does X work" queries.
Create an implementation-ready repair plan from diagnosis evidence — live-app (troubleshoot-app), backend/algo (diagnose-bug), failing URLs, logs, data-plane findings, or clearly reported breakage. Use when the user asks to "fix it", "plan this fix", or wants a plan before implementation — especially diagnose → fix-it → check-readiness → merge-it. Not for behavior-preserving structure work (refactor-it) or greenfield features without a failing contract.
Research a technical or product question before building — APIs, libraries, prior art in-repo, external docs, tradeoffs, and a recommendation. Use when the user says "research it", asks what to use, compares options, wants an RFC-style brief, or needs evidence before implementation. Read-only; spikes and dependency adds are a separate, asked-for step. Hand off to fix-it / recon issue / issues create when ready to plan or track.