Architectural Stewardship Protocol
# Architectural Stewardship Protocol A comprehensive framework for maintaining architectural integrity when working on existing software systems. ## 📋 **Overview** The Architectural Stewardship Protocol provides a systematic approach to understanding, preserving, and evolving existing codebases without compromising their architectural integrity. ## 📁 **Files** - **[template.md](template.md)** - The complete stewardship protocol template - **[example.md](example.md)** - Real-world application to a contemplative reasoning system ## 🎯 **Purpose** This protocol helps developers: - **Understand existing systems** systematically before making changes - **Preserve architectural patterns** and design principles - **Make incremental improvements** without breaking system boundaries - **Onboard new team members** to complex codebases effectively ## 🔄 **Four-Phase Methodology** ### **Phase 1: Foundational Understanding** - Load and internalize critical system documentation - Analyze core architectural components and patterns - Map integration points and system boundaries ### **Phase 2: Pattern Recognition** - Identify how core components process requests and data - Understand cross-cutting concerns and implementation strategies - Assess current development progress and integration status ### **Phase 3: Continuation Protocol** - Validate understanding of system architecture and interactions - Assess how planned changes fit within existing patterns - Apply implementation rules that preserve architectural integrity ### **Phase 4: Implementation Checklist** - Pre-implementation validation and pattern review - During-implementation boundary maintenance and documentation - Post-implementation verification and architectural compliance ## 🚀 **How to Use** 1. **For New Team Members:** - Start with Phase 1 to understand the system architecture - Work through all phases systematically before making any changes - Use the checklists to verify understanding at each step 2. **For Ongoing Development:** - Apply Phase 3 protocols before starting any new feature - Use Phase 4 checklists to maintain quality during implementation - Return to Phase 2 when facing architectural questions 3. **For AI Coding Assistants:** - Integrate the protocol rules into your AI assistant configuration - Use the systematic approach to guide AI-assisted development - Ensure AI respects existing patterns and boundaries ## 🎨 **Customization** The template includes placeholders for: - **{PROJECT_SPECIFIC_ELEMENTS}** - Replace with your system's components - **{CORE_COMPONENTS}** - Identify your system's primary architectural elements - **{INTEGRATION_POINTS}** - Map your system's key interfaces and boundaries ## 💡 **Key Principles** - **Understanding > Reading** - Focus on comprehension, not just code review - **Patterns > Individual Changes** - Preserve established architectural patterns - **Incremental > Revolutionary** - Make changes that build upon existing structure - **Documentation > Assumptions** - Document decisions and reasoning ## 🔗 **Integration with Other Prompts** **Pairs well with:** - [Project Planning/Blueprint Generator](../../project_planning/blueprint_generator/) - For new projects that need architectural frameworks - [AI Assistance/Cursor](../../../ai_assistance/cursor/) - For configuring AI tools to respect architectural boundaries ## 🤝 **Contributing** To improve this protocol: 1. Share real-world applications and examples 2. Suggest additional phases or checklist items 3. Provide feedback on effectiveness in different project contexts --- *The Stewardship Protocol transforms architectural maintenance from an ad-hoc process into a systematic, repeatable methodology.*
fill the variables
This prompt has 3 variables. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{PROJECT_SPECIFIC_ELEMENTS}{CORE_COMPONENTS}{INTEGRATION_POINTS}
Unlock with Pro →when to use it
Community prompt sourced from the open-source GitHub repo belumume/prompt-craft (MIT). A "Architectural Stewardship Protocol" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
belumume/prompt-craft · MIT
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions