Problem-Based-SRS AGENTS.md

GitHub Copilot Instructions for Problem-Based SRS

Project Overview

Problem-Based SRS is a plugin that extends your AI harness to handle Software Specifications. It plugs into GitHub Copilot first — and Claude Code and other AI coding assistants too — turning a general-purpose coding agent into one that can reason about, trace, and evolve requirements instead of only emitting code. On top of the harness it adds three things: AI‑slop prevention tuned to the specific model, a spec language and command palette that steer toward great design, and a rigorous method to evolve existing (brownfield) systems as well as build new ones.

The plugin delivers this through AgentSkills for a Problem-Based Software Requirements Specification (SRS) methodology, enabling AI-assisted requirements engineering through structured, problem-first approaches.

The repository follows the AgentSkills standard and the Claude Code Plugins layout. Compatibility priority is GitHub Copilot first, then Claude Code/Claude.ai.

Core Principles

1. Problem-First Thinking: Always identify the problem before proposing solutions
2. Lightweight Methodology: Favor simplicity over complex frameworks
3. AI-Native Design: Content designed for consumption by AI agents (following AgentSkills standard)
4. Practical Guidance: Focus on actionable skills and templates

Compatibility Priority (GHCP → Claude)

• GitHub Copilot first: Keep skills and instructions directly usable in Copilot workflows.
• Claude second: Keep .claude-plugin/plugin.json, skills/, agents/, and settings.json aligned with Claude plugin docs.
• Consistency over time: Keep compatibility guidance consistent when it changes.

Repository Structure

Problem-Based-SRS/
├── agents/
│   └── problem-based-srs/       # Agent orchestrator
│       └── AGENT.md
├── skills/
│   └── problem-based-srs/       # The single methodology skill
│       ├── SKILL.md             # Orchestrator: /problem-based-srs <action>
│       └── reference/           # One file per action (filename == action)
│           ├── business-context.md        # Step 0: Business context and principles
│           ├── problems.md                 # Step 1: WHY (customer problems)
│           ├── software-glance.md          # Step 2: High-level view
│           ├── needs.md                    # Step 3: WHAT (customer needs)
│           ├── software-vision.md          # Step 4: Architecture
│           ├── functional-requirements.md  # Step 5: HOW
│           ├── validate.md                 # Traceability validation (ZigZag)
│           ├── complexity.md               # Optional: Axiomatic Design
│           ├── live.md                     # Launch the SRS Navigator canvas (UX)
│           └── {crm,microer}-example.md    # Case study walkthroughs
├── .github/extensions/
│   └── srs-navigator/           # Canvas extension: graph UX + bundled skills
├── .spec/crm-system.json        # Demo specification for the navigator
├── docs/                        # Research papers and methodology
└── settings.json                # Default plugin settings