@open-gsd
Organization
Most AI coding setups rot as the context window fills. Open GSD keeps the context clean, the work verified, and the git history honest — ship more, worry less.
73 skills1 repository 10.8K
Start a new development milestone for an existing project. The skill gathers goals, updates project documents, optionally researches new features, and creates scoped requirements and a phased roadmap for the next cycle of work.
Route project management requests to the appropriate GSD skill. Use it to start projects, onboard existing code, manage milestones, import plans, or review backlog items without choosing the individual skill yourself.
Routes GSD project management requests to the appropriate skill for configuration, workspace management, parallel work, pausing and resuming tasks, shipping completed work, and maintenance. It also covers inbox processing, project statistics, and command guidance.
Look up available GSD commands and how to use them. Choose a quick reminder, a one-page overview, a complete reference, or help focused on a single topic.
Prepare an AI-SPEC.md design agreement for an AI development phase. The skill coordinates framework selection, documentation and domain research, and evaluation planning so the phase has a defined technical direction and assessment strategy.
Store phase documents verbatim in MemPalace, organized as decisions, plans, or milestones. Avoid duplicate entries and mirror decision or delivery facts into a knowledge graph that records when those facts became valid.
Routes quality checks to the appropriate skill, covering code review and fixes, debugging, security checks, acceptance testing, AI response evaluation, and interface reviews. It also directs requests for validating phase outputs or reviewing plans across AI systems.
Investigate failed or stuck GSD workflows using Git history, planning documents, and file state. Produce a structured diagnostic report with evidence, detected anomalies, and recommendations to help identify causes and decide corrective actions.
Plan an existing development phase around a small, usable feature. Define who needs it and why, check whether the work should be split, update ROADMAP.md, and hand off to phase planning.
Build and search a project knowledge graph, a map of information and its relationships. Check matching entries, relationship confidence, graph freshness, and changes since the previous build to understand the project's recorded structure.
Capture tasks and ideas in GSD as structured todos, notes, backlog entries, or future ideas with trigger conditions. You can also browse pending todos, choose work to start, and review previously captured future ideas.
Execute a development phase by grouping plans into waves, sets of tasks that can run together based on dependencies. Collect results, verify completion, and update progress, with options to run a selected wave or work sequentially with checkpoints.
Investigate bugs through symptom gathering and hypothesis testing, with saved investigation state across context resets. Resume earlier sessions, check their status, or request a root cause report without applying a fix.
Add tests to a completed development phase using its records and implementation. Review the proposed coverage, then generate unit tests for individual components and browser tests for full workflows, verify them, and commit the test files.
Review code changed during a project phase for bugs, security vulnerabilities, and quality issues. Choose the review depth or specific files, receive findings grouped by severity, and optionally apply fixes followed by another review.
Import an external plan into GSD after checking it against recorded project decisions, then validate the resulting plan file. It also supports converting a GSD-2 project back to the GSD v1 planning format.
Routes requests about a codebase to the appropriate skill for mapping its structure, generating knowledge graphs, updating documentation, extracting lessons, or storing and recalling project knowledge for future planning.
Close a completed development milestone by checking finished work, summarizing achievements, and archiving plans and requirements. Update project records and create a Git version tag to prepare for the next milestone.
Run an audit, separate findings that can be fixed automatically from those needing manual work, and apply eligible fixes with tests and separate commits. Use severity filters, a finding limit, or a classification-only dry run.
Explore a development idea through probing questions before committing to a plan. The skill can initiate research when needed and route the resulting ideas into GSD notes, tasks, research questions, requirements, or development phases.
Analyze an existing codebase with parallel agents and produce seven structured documents covering technology, integrations, architecture, conventions, testing, and concerns. Use the results to understand an unfamiliar project or prepare for major changes.
Prepare an existing codebase for GSD planning by mapping its structure, ingesting documentation, and initializing project records. The workflow creates or confirms planning files and produces an onboarding summary with findings and the next command to run.
Build a developer profile from past sessions or a questionnaire, then generate files and settings that personalize Claude's responses. Choose which outputs to create and compare changes when refreshing an existing profile.
Run remaining GSD project phases through discussion, planning, and execution, while recording progress and phase documents. You can limit the phase range or keep decisions interactive; after all phases finish, the workflow audits and closes the milestone.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)