dev-general-practices

Enforce foundational development practices across software projects with explicit user approval for dependencies.

4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/cuioss/plan-marshall --skill dev-general-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-general-practices
Source: https://github.com/cuioss/plan-marshall/tree/main/marketplace/bundles/plan-marshall/skills/dev-general-practices
Command: npx skills add https://github.com/cuioss/plan-marshall --skill dev-general-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes and codifies foundational development practices to improve consistency, quality, and governance across projects.

Core Features & Use Cases

  • Provides general rules for when to ask for guidance, how to research, how to select tools, and how to manage documents and dependencies.
  • Defines hard rules for tool usage to ensure deterministic behavior and prevent unsafe operations.
  • Describes how to discover, validate, and reference standards and documents.
  • Outlines related skills and standards to promote cohesive engineering practices.

Quick Start

Begin by loading the Core Development Rules, then load the relevant standards (tool usage, file operations, and search operations) as needed.

Frequently Asked Questions about dev-general-practices

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

FAQPage Schema
What are foundational development practices for standardizing software quality?

Foundational development practices standardize software quality by enforcing rules for agent development, documentation, dependency governance, and tool usage to ensure deterministic behavior across all projects.

How do I enforce code quality and governance rules across multiple projects?

You can enforce code quality and governance by codifying hard rules for tool usage, requiring explicit user approval for dependencies, and applying non-prompting tools for file and content operations across your team.

When do I need explicit user approval for managing dependencies?

Explicit user approval for dependencies is required when standardizing behavior and governance to prevent unsafe operations and ensure compliance across all software projects within a team or organization.

What is the best way to standardize documentation and research practices?

The best way to standardize documentation and research is to apply codified rules for discovering, validating, and referencing standards, while governing document proliferation within your organization.

How do non-prompting tools improve file operations in software engineering?

Non-prompting tools improve file operations by ensuring deterministic behavior and preventing unsafe actions, which standardizes content operations and maintains compliance with foundational development practices.

Do I need to load specific standards before applying these development rules?

You need to load Core Development Rules first, then load relevant standards for tool usage, file operations, and search operations as needed to ensure cohesive engineering practices across your projects.