HiIamZeref

Conducts a structured interview to create or update a repository's AGENTS.md file (the "constitution" in Spec-Driven Development) — stack, testing standards, repo conventions, workflow, and inviolable engineering principles for coding agents. ALWAYS use this skill when the user mentions creating or bootstrapping a new repository, setting up AGENTS.md or CLAUDE.md, defining a project "constitution", preparing a repo for AI-assisted or spec-driven development, or asks to document repository standards and guidelines for coding agents.

Conducts architecture discovery and system design sessions — the phase before Spec-Driven Development. Structured brainstorming, state-of-the-art research with current costs, multiple approaches with explicit tradeoffs, decision-by-decision alignment, and final consolidation into an ADR-style decision document ready to feed a Constitution and PRDs/specs. Use this whenever the user wants to brainstorm a new system, service, or feature; compare architecture approaches; discuss design tradeoffs; ask "how does the industry solve X"; or consolidate a technical discussion into a decision document — even if they never use the word "architecture". Do NOT use it for one-off technical questions that have a direct answer.