Automates architectural decision documentation in PLAN.md during brainstorming sessions.
npx skills add https://github.com/khgs2411/flow --skill flow-architect
Please help me install this Agent Skill. Skill: flow-architect Source: https://github.com/khgs2411/flow/tree/main/framework/skills/flow-architect Command: npx skills add https://github.com/khgs2411/flow --skill flow-architect
This Skill helps teams capture and document architectural decisions during brainstorming sessions using Flow framework projects. It ensures architectural rationale, DO/DON'T guidelines, and scope boundaries are preserved in PLAN.md for future reference, reducing rework during implementation.
Draft an architectural decision and capture it in PLAN.md. Example: Update the Architecture section to adopt an Event-Driven pattern for user events.
High-intent search queries and answers about installing and using this skill.
Document architectural decisions by capturing system structure, component responsibilities, and data flow directly into PLAN.md's Architecture section during brainstorming. This Skill automates the process, guiding you to record design patterns, technology choices, and rationale in consistent format for future reference and implementation traceability.
DO/DON'T guidelines are discovered patterns and anti-patterns with documented rationale that ensure consistent practices across your project. This Skill helps you propose and capture these guidelines in PLAN.md during architecture discussions, preventing rework and maintaining alignment across the team.
Record scope boundaries and technology choices explicitly in PLAN.md during brainstorming using this Skill. Documenting these decisions upfront creates a reference point for the team, reducing scope creep and ensuring implementation stays aligned with planned architecture.
Yes, this Skill is designed for Flow framework projects. It automates PLAN.md documentation during architecture brainstorming sessions, applying specifically to discussions about architecture, design patterns, technology choices, and scope definitions within the Flow workflow.
Documenting architectural rationale in PLAN.md preserves decision context and traceability that code alone cannot capture. This record helps future developers understand why specific patterns and technologies were chosen, reduces rework, and ensures consistent architectural decisions across team implementations.
claudeforgePlan software projects by guiding discovery, requirements gathering, and scoping into a structured plan.
microsoftEvaluate source code repositories for Azure deployment readiness.
endorphin-aiGuide architecture pattern selection and system design workflows.
cescrafliCapture architectural decisions as structured ADR documents with context and alternatives.
