Define architecture decisions, component decomposition, and interface contracts for software projects.
npx skills add https://github.com/tjisousa/gensem --skill design-tjisousa
Please help me install this Agent Skill. Skill: design Source: https://github.com/tjisousa/gensem/tree/main/gse-one/plugin/skills/design Command: npx skills add https://github.com/tjisousa/gensem --skill design-tjisousa
Architecture decisions, component decomposition, and interface contracts are defined and traced to support SDLC governance.
Run /gse:design to begin architecture design for the current sprint and generate the design artefact.
High-intent search queries and answers about installing and using this skill.
To document architecture decisions, use a stepwise design workflow that captures open questions, records decisions as DEC records, and persists them in structured design docs. This process ensures traceability and governance across your software development lifecycle.
Component decomposition and interface contract planning involve breaking down system modules and defining shared-state boundaries across microservices. This creates structured specifications that guide system integration and architecture governance.
Yes, you can use this for sprint planning and design reviews. It applies to both CLI and agent-based workflows, providing design validation steps and gate-based decisions to support architecture governance during these activities.
Create a decision journal for microservices by running the design workflow to generate design artifacts. It captures interface specifications and applies gate-based decisions to trace architecture choices across modules.
Yes, this works with agent-based workflows and CLI environments. It supports architecture governance and design artifact persistence across both modes, allowing flexible integration into your existing development processes.
Gate-based architecture governance requires strict adherence to design validation steps and DEC records. While it ensures traceability, it may introduce overhead for smaller projects that do not need structured decision journals or complex interface specifications.
poko8nadaGuide teams to gather requirements, define MVP scope, and break down tasks.
hachejCreate throwaway terminal and UI prototypes to validate software design decisions.
nicolasguelfiDocument architecture decisions and component interfaces for GSE-One sprints.
ofelixdevFacilitate architectural decisions with ADR documentation and trade-off analysis.
