architecture-discovery

Name: architecture-discovery
Availability: InStock
Author: oleyna80

Researches architecture options and produces an Architecture Brief before implementation planning.

Updated Jun 12, 2026

Search Tags:#planning #architecture #research #discovery #technical design #codebase analysis #sdd

Ready to run

npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill architecture-discovery-oleyna80

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-discovery
Source: https://github.com/oleyna80/agentic-sdlc-framework/tree/main/skills/architecture-discovery
Command: npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill architecture-discovery-oleyna80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new module, refactor, or integration without understanding the existing system leads to poor design decisions. This Skill turns unclear technical direction into a structured Architecture Brief before any code is written. ## Core Features & Use Cases - Read-only research workflow: Inspects repo conventions, specs, memory files, and official documentation without modifying production code. - Structured Architecture Brief: Produces a brief covering options compared, recommended approach, data model, API contracts, security constraints, risks, and acceptance criteria. - Safe boundaries: Hard-stops on package installs, credentials, production API calls, migrations, deploys, and destructive git operations. - Use Case: Before adding a new third-party payment integration, run discovery to compare provider options, review existing repo patterns, and hand off a scoped Work Block to SDD planning. ## Quick Start Ask the agent to research and compare architecture options for your planned feature and produce an Architecture Brief before writing any code.

Frequently Asked Questions about architecture-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I research architecture options before writing code?▼

Run a discovery pass that reads project context files, inspects existing repo conventions, compares practical options including keeping the current approach, and documents the recommendation in an Architecture Brief with risks and acceptance criteria.

When should I use architecture discovery versus skipping to implementation?▼

Use discovery for new projects, major modules, stack selection, API or schema design, and risky refactors. Skip it for small bugfixes, doc-only edits, minor UI changes, or tasks that already have an approved implementation plan.

What does an Architecture Brief include?▼

The brief covers the problem statement, existing system findings, research sources, options considered, recommended approach and stack, data and storage model, API contracts, security constraints, risks, acceptance criteria, and the next SDD Work Block.

Can architecture discovery install packages or call production APIs?▼

No. The workflow is read-only and hard-stops on package installs, real credentials, production API calls, migrations, deploys, destructive git operations, and production code changes unless the owner explicitly approves.

What happens after the Architecture Brief is complete?▼

The brief hands off to normal SDD planning, where Control Tower creates a scoped Work Block. The next step is task decomposition or the Plan and Discover stage of the SDD protocol.