Draft Slack-sized architecture briefs with implementation options and tradeoffs.
npx skills add https://github.com/Alfie728/my-skills --skill arch-brief
Please help me install this Agent Skill. Skill: arch-brief Source: https://github.com/Alfie728/my-skills/tree/main/arch-brief Command: npx skills add https://github.com/Alfie728/my-skills --skill arch-brief
Produces a concise, Slack-sized architecture brief to align stakeholders on an implementation approach after a user flow is approved, preventing long async debates and premature spec work.
Draft an architecture brief for the approved feature's user flow that lists two to three approaches, their pros and cons, any open questions, a huddle recommendation, and a Slack-ready summary awaiting explicit post confirmation.
High-intent search queries and answers about installing and using this skill.
A Slack architecture brief summarizes codebase context and presents two to three implementation approaches with concrete pros, cons, and open questions in a scannable message. It is prepared for posting only after explicit confirmation to ensure team alignment.
You need an architecture brief after a user flow is approved but before authoring an engineering PRD. It aligns stakeholders on a proposed implementation direction by presenting design options and tradeoffs, which prevents long async debates and premature spec work.
The best way to present design tradeoffs in Slack is generating a concise brief that lists two to three materially different approaches. Each approach includes concrete pros, cons, and open questions, alongside a recommendation on whether a huddle is needed to resolve remaining issues.
A huddle is not strictly required before posting, but the architecture brief workflow does recommend whether a team huddle is necessary based on the generated open questions. The Slack-sized message itself is only posted after explicit confirmation from the user.
Yes, you can summarize codebase context directly into a Slack-ready architecture brief. The process grounds the design options and tradeoffs in the existing codebase, producing a short, scannable message tailored for Slack to quickly align stakeholders on the implementation approach.
btabaskaIdentify entry points, data flow, and ownership for a codebase area.
qa-amanDraft a structured PRD from a brief or problem statement.
NimbleBrainIncSend and schedule Slack messages with API authorization.
vladm3105Generate Mermaid architecture diagrams and embed SVG previews in technical documents.
