arckit-cli 6.1.1__py3-none-any.whl

arckit_cli-6.1.1.data/data/share/arckit/docs/guides/gcloud-competitors.md

@@ -0,0 +1,61 @@
+# G-Cloud Competitor Benchmark Guide
+
+> **Guide Origin**: Community | **ArcKit Version**: [VERSION]
+
+`/arckit:gcloud-competitors` benchmarks a supplier-side G-Cloud service against comparable Digital
+Marketplace rivals. It uses the service design, SDD, pricing, and optional market intelligence to
+produce positioning, differentiation, and improvement evidence.
+
+---
+
+## Command
+
+```bash
+/arckit:gcloud-competitors <service project or service name>
+```
+
+Output:
+
+```text
+projects/<NNN>-<service-name>/ARC-<NNN>-GCMP-v1.0.md
+```
+
+---
+
+## When to Use
+
+- After service design, SDD, and pricing are drafted.
+- Before final review, to test whether features, benefits, and price positioning are credible.
+- When a supplier wants to understand marketplace rivals for the same lot or capability.
+- When existing `/arckit:tenders` or `/arckit:competitors` artefacts can enrich the analysis.
+
+---
+
+## Inputs
+
+| Input | Purpose |
+|-------|---------|
+| Service design (`SVCD`) | Proposition, target buyers, features, benefits, and lot |
+| SDD (`SDD`) | Marketplace-facing claims and support model |
+| Pricing (`PRIC`) | Price tiers, assumptions, discounts, and options |
+| Tender or competitor artefacts | Optional award and supplier evidence |
+
+---
+
+## Output Sections
+
+| Section | Purpose |
+|---------|---------|
+| Rival set | Comparable services and suppliers |
+| Feature comparison | Strengths, gaps, and differentiators |
+| Price positioning | Where the service sits against public comparators |
+| Submission improvements | Specific updates to service design, SDD, pricing, or security |
+| Caveats | Limits of public marketplace evidence |
+
+---
+
+## Related Commands
+
+- `/arckit:tenders` - Procurement market intelligence.
+- `/arckit:competitors` - Supplier landscape intelligence.
+- `/arckit:review` - Check readiness after benchmark-driven updates.

arckit_cli-6.1.1.data/data/share/arckit/docs/guides/gcloud-search.md

@@ -0,0 +1,106 @@
+# G-Cloud Search Playbook
+
+> **Guide Origin**: Official | **ArcKit Version**: [VERSION]
+
+`/arckit:gcloud-search` finds G-Cloud services on the UK Digital Marketplace with live search and comparison capabilities.
+
+---
+
+## Inputs
+
+| Artefact | Purpose |
+|----------|---------|
+| Requirements (`ARC-<id>-REQ-v1.0.md`) | What capabilities are needed |
+| Architecture principles | Technology and vendor standards |
+| Budget constraints | Pricing parameters |
+
+---
+
+## Command
+
+```bash
+/arckit:gcloud-search Find G-Cloud services for <requirement>
+```
+
+Output: `projects/<id>/ARC-<id>-GCLD-v1.0.md`
+
+---
+
+## Search Results Structure
+
+| Section | Contents |
+|---------|----------|
+| Search Parameters | Keywords, categories, filters used |
+| Service Summary | Overview of matching services |
+| Service Comparison | Side-by-side comparison table |
+| Pricing Analysis | Cost comparison and models |
+| Compliance Summary | Certifications and security ratings |
+| Recommendation | Shortlist for further evaluation |
+
+---
+
+## G-Cloud Categories (Lots)
+
+| Lot | Description | Examples |
+|-----|-------------|----------|
+| Cloud Hosting | Infrastructure services | AWS, Azure, GCP |
+| Cloud Software | SaaS applications | CRM, collaboration tools |
+| Cloud Support | Professional services | Migration, training |
+
+---
+
+## Key Filters
+
+| Filter | Purpose |
+|--------|---------|
+| Service Category | Narrow by service type |
+| Supplier Size | SME vs large enterprise |
+| Security Clearance | SC, DV cleared suppliers |
+| Data Location | UK, EU, global |
+| Certifications | ISO 27001, Cyber Essentials+ |
+
+---
+
+## One-Page Workflow
+
+| Phase | Key Activities | ArcKit Commands |
+|-------|----------------|-----------------|
+| Requirements | Define what's needed | `/arckit:requirements` |
+| Search | Find matching services | `/arckit:gcloud-search` |
+| Shortlist | Compare and select candidates | Manual review |
+| Clarify | Ask suppliers questions | `/arckit:gcloud-clarify` |
+| Evaluate | Score and select | `/arckit:evaluate` |
+
+---
+
+## Review Checklist
+
+- Search keywords match requirement terminology.
+- Multiple service categories explored.
+- SME suppliers included in search.
+- Security certifications filtered appropriately.
+- Data location requirements considered.
+- Price ranges captured for comparison.
+- At least 3 services shortlisted for evaluation.
+
+---
+
+## Digital Marketplace Tips
+
+| Tip | Description |
+|-----|-------------|
+| Keyword Variation | Try synonyms and alternative terms |
+| Category Browse | Browse categories, don't just search |
+| Supplier Filter | Filter by size to include SMEs |
+| Feature Filter | Use feature checkboxes to narrow |
+| Price Sort | Sort by price to understand range |
+
+---
+
+## Key Principles
+
+1. **Fair Competition**: Search broadly to find all suitable services.
+2. **SME Consideration**: Government aims for 33% SME spend.
+3. **Requirement Focus**: Search based on needs, not familiar vendors.
+4. **Document Everything**: Record search criteria for audit trail.
+5. **Compare Fairly**: Use consistent criteria across services.

arckit_cli-6.1.1.data/data/share/arckit/docs/guides/gcp-research.md

@@ -0,0 +1,169 @@
+# Google Cloud Technology Research Guide
+
+> **Guide Origin**: Official | **ArcKit Version**: [VERSION]
+
+`/arckit:gcp-research` researches Google Cloud services, architecture patterns, and implementation guidance using the Google Developer Knowledge MCP server for authoritative documentation.
+
+> **Agent Architecture**: This command runs as an autonomous agent via the Task tool. The agent makes 15-30+ MCP calls to gather Google Cloud documentation in its own context window, keeping the main conversation clean. The slash command is a thin wrapper that delegates to the agent.
+
+---
+
+## Prerequisites
+
+### Google Developer Knowledge MCP Server (REQUIRED)
+
+This command **requires** the Google Developer Knowledge MCP server to be installed. It will not work without it.
+
+**API Key Required**: Unlike AWS Knowledge and Microsoft Learn MCPs (which are free/unauthenticated), the Google Developer Knowledge MCP requires an API key. Get one from [Google AI Studio](https://aistudio.google.com/apikey) or the [Google Cloud Console](https://console.cloud.google.com/apis/credentials).
+
+**Installation**:
+
+Add to your Claude Code MCP configuration (`~/.claude/claude_desktop_config.json` or project `.mcp.json`):
+
+```json
+{
+  "mcpServers": {
+    "google-developer-knowledge": {
+      "type": "http",
+      "url": "https://developerknowledge.googleapis.com/mcp",
+      "headers": {
+        "X-Goog-Api-Key": "${GOOGLE_API_KEY}"
+      }
+    }
+  }
+}
+```
+
+Set the environment variable:
+
+```bash
+export GOOGLE_API_KEY="your-api-key-here"
+```
+
+After installation, restart Claude Code to load the MCP server.
+
+**Slow corporate network?** On TLS-inspecting proxies, VPN tunnels, or congested links, large-scope research prompts can exceed Claude Code's default per-request fetch timeout. Set `MCP_TOOL_TIMEOUT=300000` (5 minutes, in milliseconds) before launching Claude — see [MCP per-request timeout](mcp-servers.md#optional-mcp-per-request-timeout-claude-code-v21142) in the MCP setup guide. Requires Claude Code v2.1.142+.
+
+### Project Prerequisites
+
+- Requirements document (`ARC-*-REQ-*.md`) - **MANDATORY**
+- Data model (`ARC-*-DATA-*.md`) - Recommended for database selection
+- Stakeholders (`ARC-*-STKE-*.md`) - Recommended for priorities
+
+---
+
+## Scenario Matrix
+
+| Scenario | Prompt seed | Focus |
+|---------|-------------|-------|
+| Service selection | "Research Google Cloud services for <capability>" | Maps requirements to Google Cloud services |
+| Architecture pattern | "Research Google Cloud architecture pattern for <pattern>" | Reference architectures from Architecture Center |
+| UK Government | "Research Google Cloud for UK Government <project>" | G-Cloud, europe-west2, NCSC compliance |
+| AI/ML workloads | "Research Google Cloud AI services for <use case>" | Vertex AI, Gemini API |
+| Migration | "Research Google Cloud migration options for <workload>" | Migrate to GCP, modernization paths |
+| Security assessment | "Research Security Command Center for <domain>" | SCC mapping, Architecture Framework security |
+| Data analytics | "Research Google Cloud data platform for <use case>" | BigQuery, Dataflow, Pub/Sub |
+
+Add constraints (budget, classification, region) in the prompt for tailored results.
+
+---
+
+## Command
+
+```bash
+/arckit:gcp-research Research Google Cloud services for <project>
+```
+
+Outputs: `projects/<id>/research/ARC-<id>-GCRS-v1.0.md`
+
+> **Auto-versioning**: Re-running this command when a document already exists automatically increments the version (minor for refreshed content, major for changed scope) instead of overwriting.
+
+---
+
+## Long runs: Remote Control + push notifications
+
+`/arckit:gcp-research` frequently exceeds 10 minutes as the agent issues dozens of Google Developer Knowledge MCP calls and fetches full documentation pages for cost and compliance analysis. To avoid babysitting the terminal, pair it with [Claude Code Remote Control](https://code.claude.com/docs/en/remote-control):
+
+```bash
+claude remote-control
+```
+
+Drive the session from claude.ai/code or the mobile app, then enable `/config → Push when Claude decides` so your phone gets a notification on completion or when the agent reaches a decision point (service shortlist confirmation, region selection). ArcKit's minimum Claude Code floor (v2.1.121) already covers the v2.1.110 RC requirement.
+
+Caveats: Pro/Max plans only (no API keys, no Bedrock/Vertex/Foundry), push is a single on/off so chatty agents can over-notify, and the local `claude` process must keep running.
+
+---
+
+## MCP Tools Used
+
+The command uses three Google Developer Knowledge MCP tools:
+
+| Tool | Purpose |
+|------|---------|
+| `search_documents` | Search Google Cloud documentation for services, patterns, best practices |
+| `get_document` | Retrieve complete documentation pages for detailed analysis |
+| `batch_get_documents` | Fetch multiple related documentation pages in a single call |
+
+---
+
+## Output Highlights
+
+- **Google Cloud Service Recommendations**: Mapped to specific requirements (FR, NFR, INT, DR)
+- **Architecture Pattern**: Reference architecture from Google Cloud Architecture Center
+- **Architecture Framework Assessment**: All 6 pillars evaluated per service
+- **Security Command Center**: Finding categories and CIS Benchmark for GCP
+- **UK Government Compliance**: G-Cloud, europe-west2 region, NCSC principles
+- **Cost Estimates**: Monthly and 3-year TCO with optimization recommendations
+- **Implementation Guidance**: Terraform templates, Cloud Build pipelines
+
+---
+
+## UK Government Features
+
+When UK Government project detected:
+
+| Area | Coverage |
+|------|----------|
+| **G-Cloud** | Framework reference, service IDs, procurement steps |
+| **Data Residency** | europe-west2 (London) availability, cross-region replication |
+| **Classification** | OFFICIAL, OFFICIAL-SENSITIVE suitability |
+| **NCSC** | 14 Cloud Security Principles alignment |
+| **Note** | No Google Cloud Government UK (US-only) — not suitable for SECRET |
+
+---
+
+## Follow-on Actions
+
+- Feed Google Cloud findings into `/arckit:diagram` for GCP architecture diagrams
+- Run `/arckit:secure` to validate against UK Secure by Design
+- Run `/arckit:devops` to plan Cloud Build CI/CD pipelines
+- Run `/arckit:finops` to create Google Cloud FinOps cost management strategy
+- Run `/arckit:adr` to document Google Cloud service selection decisions
+
+---
+
+## Comparison with /arckit:research
+
+| Feature | `/arckit:research` | `/arckit:gcp-research` |
+|---------|-------------------|------------------------|
+| Scope | Multi-cloud, SaaS, open-source | Google Cloud-specific only |
+| Source | Web search, multiple sources | Google Developer Knowledge MCP (authoritative) |
+| Depth | Build vs buy analysis | Deep Google Cloud service analysis |
+| Compliance | General UK Gov | Google Cloud-specific UK compliance |
+| Code samples | Limited | Terraform, Cloud Build |
+| Cost estimates | High-level | Detailed Google Cloud pricing |
+
+**When to use which**:
+
+- Use `/arckit:research` for cloud-agnostic evaluation or build vs buy
+- Use `/arckit:gcp-research` when Google Cloud is the target platform
+
+---
+
+## Resources
+
+- [Google Developer Knowledge MCP](https://developerknowledge.googleapis.com/mcp) - MCP server endpoint
+- [Google Cloud Architecture Center](https://cloud.google.com/architecture) - Reference architectures
+- [Google Cloud Architecture Framework](https://cloud.google.com/architecture/framework) - Design guidance
+- [Google Cloud Security Best Practices](https://cloud.google.com/security/best-practices) - Security controls
+- [Google Cloud UK Compliance](https://cloud.google.com/security/compliance/offerings#/regions=Europe) - UK Government compliance

arckit_cli-6.1.1.data/data/share/arckit/docs/guides/glossary.md

@@ -0,0 +1,190 @@
+# Glossary Guide
+
+> **Guide Origin**: Official | **ArcKit Version**: [VERSION]
+
+`/arckit:glossary` consolidates terms, acronyms, and definitions from all project artifacts into a single authoritative reference document.
+
+---
+
+## Purpose
+
+Architecture projects accumulate terminology across dozens of artifacts: requirements introduce domain-specific language, data models define entity names, stakeholder analyses reference governance bodies, and business cases use financial jargon. Without a single source of truth for terminology, teams suffer from:
+
+- **Ambiguity** -- the same term means different things to different people
+- **Onboarding friction** -- new team members spend weeks decoding project-specific language
+- **Inconsistent language** -- artifacts use different terms for the same concept
+
+The `/arckit:glossary` command **extracts and consolidates** all terminology from existing artifacts into a structured glossary that:
+
+- Provides a shared vocabulary for the entire project team
+- Reduces miscommunication between business and technical stakeholders
+- Onboards new team members quickly with clear, authoritative definitions
+- Ensures consistent language across all architecture artifacts
+- Flags terminology inconsistencies found across documents
+
+---
+
+## Inputs
+
+| Artifact | Requirement | What It Provides |
+|----------|-------------|------------------|
+| Requirements Specification | Recommended | Domain terms, requirement ID prefixes, technical/business terms, acronyms |
+| Data Model | Recommended | Entity names, attribute definitions, data types, relationship terminology |
+| Stakeholder Analysis | Optional | Role titles, organizational terms, governance bodies |
+| Architecture Principles | Optional | Principle names, governance terminology, compliance terms |
+| Strategic Business Case | Optional | Financial/business terms, investment terminology |
+| Research Report | Optional | Technology terms, vendor-specific terminology, industry standards |
+| Architecture Decision Records | Optional | Architectural pattern names, technology choices |
+| Architecture Strategy | Optional | Strategic themes, capability terms, maturity model terminology |
+| Risk Register | Optional | Risk categories, mitigation terms, likelihood/impact terminology |
+
+> **Note**: The more artifacts available, the more comprehensive the glossary. At minimum, have requirements or a data model in place before running.
+
+---
+
+## Command
+
+```bash
+/arckit:glossary Generate glossary for <project-name>
+```
+
+Outputs: `projects/<id>/ARC-<id>-GLOS-v1.0.md`
+
+---
+
+## Glossary Structure
+
+| Section | Contents |
+|---------|----------|
+| **Document Control** | Document ID, version, owner, classification, review cycle |
+| **Business Terms** | Domain-specific business terminology with definitions |
+| **Technical Terms** | Architecture patterns, technology terms, standards |
+| **Governance Terms** | Compliance frameworks, assessment criteria, maturity levels |
+| **Financial Terms** | Investment terminology, procurement vehicle names |
+| **Data Terms** | Entity names, attribute definitions, data types |
+| **Security Terms** | Security standards, classification levels, access control terms |
+| **Acronyms and Abbreviations** | Quick-reference table of all acronyms with expansions |
+| **Standards Referenced** | Named standards with versions and URLs |
+| **Cross-Reference Index** | Related terms linked for navigation |
+| **Consistency Notes** | Terms with conflicting definitions across artifacts |
+
+---
+
+## Workflow Position
+
+The glossary command sits at a consolidation point in the ArcKit workflow -- it reads existing artifacts to extract terminology:
+
+```text
+┌──────────────┐    ┌─────────────┐    ┌──────────────┐
+│ Requirements │    │  Data Model │    │ Stakeholders │
+└──────┬───────┘    └──────┬──────┘    └──────┬───────┘
+       │                   │                  │
+       └───────────────────┼──────────────────┘
+                           │
+                           ▼
+                ┌─────────────────────┐
+                │  /arckit:glossary   │
+                └──────────┬──────────┘
+                           │
+              ┌────────────┼────────────┐
+              ▼                         ▼
+       ┌──────────────┐         ┌─────────────┐
+       │ Presentation │         │  Framework  │
+       └──────────────┘         └─────────────┘
+```
+
+**Best Practice**: Create the glossary AFTER you have built several artifacts (requirements, data model, stakeholders at minimum). The glossary extracts terminology -- it needs source material to work from.
+
+---
+
+## Example Usage
+
+### Minimal (Requirements only)
+
+```bash
+# Ensure at least one artifact exists
+/arckit:requirements Create requirements for Smart Meter App
+
+# Generate glossary from available artifacts
+/arckit:glossary Generate glossary for Smart Meter App
+```
+
+### Comprehensive (Many artifacts available)
+
+```bash
+# Create multiple artifacts first
+/arckit:requirements Create requirements for Fuel Price Service
+/arckit:data-model Create data model for Fuel Price Service
+/arckit:stakeholders Analyze stakeholders for Fuel Price Service
+/arckit:principles Create principles for Fuel Price Service
+/arckit:sobc Create business case for Fuel Price Service
+/arckit:research Research technology options for Fuel Price Service
+/arckit:adr Record decision on API gateway for Fuel Price Service
+
+# Generate comprehensive glossary
+/arckit:glossary Generate glossary for Fuel Price Service
+```
+
+---
+
+## Tips
+
+- **Run after multiple artifacts exist**: The glossary extracts terminology from existing documents. The more artifacts available, the more comprehensive and useful the glossary will be.
+
+- **Update as new artifacts are created**: When you add new artifacts (ADRs, risk registers, research reports), re-run the glossary command to capture new terminology. A new version (v2.0) will be created.
+
+- **Use "all projects" scope for cross-project glossaries**: Run `/arckit:glossary Generate glossary for all projects` to create a consolidated glossary across all project directories, saved in `projects/000-global/`.
+
+- **Review with domain experts**: The glossary infers definitions from artifact context. Have domain experts validate definitions, especially for business-specific terms that may have organisation-specific meanings.
+
+- **Resolve inconsistencies**: The glossary flags terms defined differently across artifacts. Use these flags as a prompt to align terminology across your project.
+
+---
+
+## Follow-On Commands
+
+After creating the glossary, typical next steps include:
+
+| Command | Purpose |
+|---------|---------|
+| `/arckit:data-model` | Review data model using validated entity/attribute names from glossary |
+| `/arckit:framework` | Create assessment framework with consistent terminology |
+
+---
+
+## Output Example
+
+```text
+## Project Glossary Created
+
+**Document**: `projects/017-fuel-prices/ARC-017-GLOS-v1.0.md`
+**Document ID**: ARC-017-GLOS-v1.0
+
+### Glossary Overview
+- **Total Terms Defined**: 87
+- **Acronyms Catalogued**: 34
+- **Standards Referenced**: 12
+- **Source Artifacts Scanned**: 5
+
+### Terms by Category
+- **Business**: 18 terms
+- **Technical**: 24 terms
+- **Governance**: 11 terms
+- **Financial**: 9 terms
+- **Data**: 16 terms
+- **Security**: 9 terms
+
+### Source Artifacts
+- ARC-017-REQ-v1.0.md (Requirements Specification)
+- ARC-017-DATA-v1.0.md (Data Model)
+- ARC-017-STKE-v1.0.md (Stakeholder Analysis)
+- ARC-017-SOBC-v1.0.md (Strategic Business Case)
+- ARC-000-PRIN-v1.0.md (Architecture Principles)
+
+### Coverage Gaps
+- Risk Register not available (would add risk/mitigation terminology)
+- Research Report not available (would add vendor/technology terminology)
+- 3 terms flagged with ambiguous definitions requiring expert review
+
+**File location**: `projects/017-fuel-prices/ARC-017-GLOS-v1.0.md`
+```

arckit_cli-6.1.1.data/data/share/arckit/docs/guides/gov-code-search.md

@@ -0,0 +1,119 @@
+# Government Code Search Guide
+
+> **Guide Origin**: Official | **ArcKit Version**: 4.4.0
+
+`/arckit:gov-code-search` provides general-purpose natural language search across 24,500+ UK government open-source repositories, returning matching repositories, patterns, and implementation approaches without requiring an active project.
+
+> **Agent Architecture**: This command runs as an autonomous agent via the Task tool. The agent performs multiple govreposcrape searches, uses WebFetch to inspect top results on GitHub, and synthesises findings into a structured report, keeping the main conversation clean. The slash command is a thin wrapper that delegates to the agent.
+
+---
+
+## Prerequisites
+
+### govreposcrape MCP Server (AUTO-INSTALLED)
+
+This command uses the govreposcrape MCP server which is **automatically included** with the ArcKit plugin. No manual setup required.
+
+**Endpoint**: `https://govreposcrape-api-1060386346356.us-central1.run.app/mcp`
+
+### Project Prerequisites
+
+Project context is **OPTIONAL** for this command. It can be run without any existing ArcKit project to perform exploratory research.
+
+- Requirements document (`ARC-*-REQ-*.md`) - Optional (used when available to focus results)
+- Architecture principles (`ARC-000-PRIN-*.md`) - Optional
+
+---
+
+## Scenario Matrix
+
+| Scenario | Prompt seed | Focus |
+|---------|-------------|-------|
+| Implementation discovery | "How did gov teams implement `<X>`?" | Real-world implementations and approaches |
+| Technology survey | "Who uses `<Y>` technology in UK government?" | Adoption across departments |
+| Pattern research | "Show me government examples of `<pattern>`" | Design and architectural patterns |
+| Standards discovery | "Find government implementations of `<standard>`" | Standard adoption and compliance examples |
+| Framework comparison | "Compare government use of `<framework A>` vs `<framework B>`" | Framework adoption and trade-offs |
+
+Add domain qualifiers (NHS, HMRC, MoD, GDS) in the prompt to narrow results to specific departments or sectors.
+
+---
+
+## Command
+
+```bash
+/arckit:gov-code-search <query>
+```
+
+Outputs: `projects/<id>/research/ARC-<id>-GOVS-v1.0.md` (if a project exists), or to a timestamped file in the current directory.
+
+> **Auto-versioning**: Re-running this command when a document already exists automatically increments the version.
+
+---
+
+## Search Tips
+
+Govreposcrape uses semantic search, so query quality directly affects result quality:
+
+| Tip | Example |
+|-----|---------|
+| Be descriptive and domain-specific | "NHS FHIR API patient data integration" (not "API") |
+| Include the technology and context | "Django REST framework benefit payment service" |
+| Name the department or sector | "HMRC self-assessment tax calculation" |
+| Use full names, not acronyms alone | "Government Digital Service design system components" |
+| Describe the problem, not just the solution | "real-time vehicle location tracking public transport" |
+
+Avoid vague single-word queries such as "authentication" or "database" — these return too many unrelated results.
+
+---
+
+## How It Works
+
+The agent issues multiple query variations against the govreposcrape semantic search API:
+
+| Step | Action |
+|------|--------|
+| 1 | Generate 3-5 semantically varied queries from the user's input |
+| 2 | Run each query against govreposcrape, collecting top results |
+| 3 | De-duplicate and rank repositories by relevance score |
+| 4 | Fetch GitHub repo details via WebFetch for the top candidates |
+| 5 | Summarise patterns, languages, and licensing across results |
+
+---
+
+## Output Highlights
+
+- **Search results** ranked by semantic relevance with repository profiles
+- **Repository profiles** including language, license, last commit, and activity level
+- **Implementation patterns** observed across matching repositories
+- **Departmental adoption** showing which government organisations have tackled similar problems
+- **Key findings** and recommended repositories to inspect further
+
+---
+
+## Follow-on Actions
+
+- Run `/arckit:gov-reuse` to perform a full scored reuse assessment for a specific project
+- Run `/arckit:research` to broaden the search to commercial and open-source options
+- Run `/arckit:adr` to document technology or pattern decisions informed by findings
+
+---
+
+## Comparison with /arckit:gov-reuse and /arckit:gov-landscape
+
+| Feature | `/arckit:gov-code-search` | `/arckit:gov-reuse` | `/arckit:gov-landscape` |
+|---------|--------------------------|--------------------|-----------------------|
+| Purpose | Search and discover | Assess and score for reuse | Map an entire domain |
+| Project required | No | Yes (requirements MANDATORY) | No (recommended) |
+| Output | Search results + repo profiles | Scored reuse assessment | Domain landscape map |
+| Scoring | None (relevance only) | 5-criteria scored assessment | Maturity scoring per org |
+| When to use | Exploratory research | Before building a capability | Understanding a whole domain |
+
+**Workflow**: Use `/arckit:gov-code-search` for quick discovery, `/arckit:gov-reuse` for project-specific reuse decisions, and `/arckit:gov-landscape` for domain-level situational awareness.
+
+---
+
+## Resources
+
+- [govreposcrape](https://github.com/chrisns/govreposcrape) - Semantic search over UK government repositories
+- [govreposcrape API](https://govreposcrape-api-1060386346356.us-central1.run.app/openapi.json) - OpenAPI specification