Synthesize a high-level Software Glance from Customer Problems.
npx skills add https://github.com/shirogin/jesuph-skills --skill software-glance
Please help me install this Agent Skill. Skill: software-glance Source: https://github.com/shirogin/jesuph-skills/tree/main/.agents/skills/software-glance Command: npx skills add https://github.com/shirogin/jesuph-skills --skill software-glance
Transforms Customer Problems into an initial Software Glance, providing a conceptual view of the solution that guides boundary setting and subsequent steps in the Problem-Based SRS workflow.
Analyze the Customer Problems and produce a high-level Software Glance that defines system boundaries, actors, components, interfaces, and data considerations.
High-intent search queries and answers about installing and using this skill.
To turn customer problems into system boundaries and interfaces, you synthesize a high-level Software Glance that defines main components, actors, and external system integrations. This conceptual view guides subsequent problem-based SRS workflow steps.
A Software Glance in problem-based SRS is a high-level abstract view of a solution derived from customer problems. It outlines system boundaries, actors, components, interfaces, and data considerations while avoiding detailed requirements and architecture decisions.
You define actors and components from customer problems by synthesizing them into a conceptual Software Glance. This process identifies external system integrations and outlines data considerations to support traceability for subsequent software design steps.
No, the Software Glance process explicitly avoids detailed requirements and architecture decisions. It satisfies conceptual design requirements by providing a high-level abstract view of system boundaries, actors, and interfaces instead of deep technical specifications.
You need to generate a Software Glance after identifying customer problems in step one of a problem-based SRS workflow. It serves as the transition point to set system boundaries and guide subsequent detailed requirement steps.
Yes, you can use this method to outline data considerations for software design. Synthesizing customer problems into a Software Glance cross-cuts customer problem traceability and explicitly defines data considerations for subsequent steps.
RafaelGorskiGuide a 5-step SRS methodology linking requirements to business problems.
takemo101Generate foundational system design documents in Japanese with Mermaid diagrams.
peterbamuhigireGenerate SRS Section 1.0 from vision and glossary markdown files.
shafibabarCreates a C4 Level 1 System Context Diagram identifying human actors and external system dependencies.
