Document architecture decisions and component interfaces for GSE-One sprints.
npx skills add https://github.com/nicolasguelfi/gensem --skill design-nicolasguelfi
Please help me install this Agent Skill. Skill: design Source: https://github.com/nicolasguelfi/gensem/tree/main/gse-one/plugin/skills/design Command: npx skills add https://github.com/nicolasguelfi/gensem --skill design-nicolasguelfi
Design decisions and architecture governance for the GSE-One plugin, ensuring consistent interfaces, scalable components, and traceable decisions across sprints.
Run the GSE-One design workflow to draft an architecture plan for the current sprint.
High-intent search queries and answers about installing and using this skill.
To document architecture decisions for a sprint, use a DEC-based governance approach to capture rationale and traceability. This ensures design constraints like non-circular dependencies and security considerations are recorded for future audits.
Component decomposition is the process of breaking down system modules into explicit interfaces and boundaries. It prevents architectural drift by defining clear interactions and enforcing design constraints like avoiding shared state across components.
Scope analysis identifies components and cross-cutting concerns by evaluating sprint requirements. It guides the breakdown of modules into explicit interfaces and DEC records, ensuring all dependencies and security considerations are traceable.
Yes, this approach is applicable to sprint-level design activities across modules. It guides scope analysis, component breakdown, interface definition, and traceable DEC records while persisting artifacts in designated directories.
DEC-based governance requires strict adherence to enforced design constraints, including non-circular dependencies and shared state limitations. It may not suit projects lacking clear module boundaries or those needing rapid, unrecorded architectural changes.
Architecture governance requires persisting artifacts in specific directories to maintain traceability and ensure design decisions are accessible for future audits. This practice enforces consistent interfaces and scalable components across sprints.
dikiniAuthor formal architecture and design specifications for software components and interfaces.
514-labsValidate DEC Bench prerequisites and execute the first benchmark scenario.
HungNthGuide WordPress plugin development with architecture, hooks, and security practices.
dralgorhythmDocument architectural decisions using ADR format with Title, Status, Context, Decision, Rationale, and Consequences.
