Agent skill · operations · thienanblog
project-development-mindset
Primary coordinator for repository implementation, diagnosis, verification, and durable changes to code, configuration, tests, or documentation. Use first for ordinary project work; inspect before routing to at most one specialist for the current primary concern. Do not use for general explanations, passive inspection with no project-work outcome, or the independent brainstorm-first decision phase unless explicitly invoked.
Why this skill is useful
Provides a structured approach to project development that emphasizes reuse, maintainability, and proportionate changes, which the AI may not inherently know.
What it needs
About 9k tokens when loaded. Last updated 2026-08-05. 63 stars on the source repository.
What this skill does
Project Development Mindset Use this skill as an adaptive baseline, not mandatory ceremony. Apply only the guidance relevant to the task. Scale discovery, planning, implementation, and verification to the task's impact, uncertainty, and reversibility. Precedence And Adaptation Follow system instructions, the user's current request, and applicable project instructions before this general guidance. Treat repository conventions as evidence of project intent, not as rules to copy blindly when they conflict with correctness, security, maintainability, or a more authoritative instruction. Start with this coordinator instead of preloading every possibly relevant specialist. After initial orientation, load at most one specialist for the current primary concern. Keep this skill only as the cross-cutting baseline, and switch specialists rather than stacking workflows when the primary concern changes. Apply routine gates implicitly for small, local work. Do not turn them into user-facing ceremony unless a decision or risk needs discussion. Preserve unrelated user changes and existing work. Do not clean up, revert, or broaden scope merely because nearby code could be improved. Run in the main conversation by default. Before spawning any subagent, agent team, or delegated worker, explain that delegation can increase usage and ask the user to approve the proposed agent count and scope. Ask again before expanding an approved scope. Core Outcomes Aim for all of the following: Understand the project context that materially affects the requested behavior. Define what success means before making a substantial change. Implement the smallest coherent change that fully solves the task. Reuse existing project surfaces when their semantics and boundaries fit. Verify behavior with evidence proportionate to the likely failure cost. Keep durable sources of truth aligned when the change materially affects them. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills thienanblog/project-development-mindset