TedToolkit Project Development

Plugin tedtoolkit-project-development from marketplace tedtoolkit-skills in TedToolkit/skills. Commands read from the repo's manifest — yesterday.

Skills (20)

• architecture-design

  Decide and record current architecture or an enduring technical choice. Use when system boundaries, dependency direction, cross-cutting behavior, quality attributes, technology selection, or an ADR needs durable rationale, alternatives, consequences, evidence, and ownership.

• change-design

  Deprecated compatibility alias for explicit $change-design invocations. Route the request to design-change; do not select this alias for ordinary change-design requests.

• continue-change

  Resume one explicitly identified format-3 change from its persisted state and route exactly one user-authorized next phase. Use when the user references or @-mentions a change.md and asks to approve it, continue, resume, proceed, or determine the next step. Reconstruct state from the change and work

• design-change

  Clarify, classify, and design exactly one coherent product or library change. Use directly when a request already expresses one bounded change, after scope-changes establishes a candidate, or when resuming or revising one explicitly identified existing change. Investigate repository evidence, ask hi

• design-principles

  Govern recurring architecture and engineering trade-offs with repository design principles. Use when a stable default, rationale, strength, scope, review trigger, or exception route must be created, revised, retired, or distinguished from a one-off architecture decision.

• implement-change-tdd

  Deprecated compatibility alias for explicit $implement-change-tdd invocations. Route the request to implement-change; do not select this alias for ordinary implementation requests.

• implement-change-work-items

  Deprecated compatibility alias for explicit $implement-change-work-items invocations. Route the original request to orchestrate-work-items; do not select this alias for ordinary orchestration.

• implement-change

  Implement one approved Fast plan, Standard change, single-delivery Controlled change, or selected Controlled work item with proof scaled to its change kind and risk. Use for behavior changes, bug fixes, behavior-preserving refactors, maintenance, migrations, and bounded experiments. Choose the loop

• library-product-intent

  Define the durable product intent of a reusable software library. Use when its target consumers, problem, value, or non-goals are unclear or changing, or when principles, architecture, and change design need an approved product baseline.

• orchestrate-work-items

  Coordinate execution and verified integration for every Controlled change with two or more approved work items. Run dependency or collision constrained waves serially; parallelize only when at least two ready isolated workers provide material value. Scale independent candidate review to material Con

• plan-work-items

  Slice one approved Controlled change into two or more independently verifiable human work items. Use only when one embedded delivery brief cannot honestly implement and prove the approved goal, or when a multi-item dependency map is required. Decide this from the approved contract rather than asking

• prepare-change

  Deprecated compatibility alias for explicit $prepare-change invocations. Route the original request to scope-changes; do not select this alias for ordinary request scoping.

• project-scaffolding

  Scaffold or reorganize .NET repositories, solutions, projects, dependency boundaries, MSBuild controls, and slnx views. Use when creating a library or solution, adding or splitting a project, selecting folders, reviewing shared build controls, or supplying an approved location needed by another proj

• review-change-design

  Independently review a Standard or Controlled change for correct profile, one coherent goal, human handoff quality, behavioral or invariant completeness, scalable proof, constraints, risks, ADR coverage, and readiness for approval. Use before approving Controlled changes and whenever a draft may be

• review-code

  Audit one production-code correctness lane against an approved delivery contract and its actual risk. Use when review-implementation dispatches the lane or when the user explicitly asks for code-only correctness, failure semantics, compatibility, dependency direction, resource, concurrency, maintain

• review-implementation

  Plan, coordinate, and synthesize a risk-scaled implementation review for an approved Fast plan, Standard or Controlled delivery, selected work item, or integrated multi-item change. Use exact candidate-bound code, test, and verification lanes; establish reviewer independence when risk requires it; r

• review-tests

  Audit one test-adequacy lane for whether changed or relied-upon tests credibly prove an approved behavior, regression, invariant, boundary, compatibility rule, or journey. Use when review-implementation dispatches the lane or when the user explicitly asks for test-only scope, partitions, assertion s

• scope-changes

  Scope an ambiguous or multi-outcome product or library request into zero, one, or several coherent changes before implementation. Use when outcomes, ownership, dependencies, or release boundaries are genuinely unclear. Do not use for an already bounded change, a failing named project, or an explicit

• verify-implementation

  Execute an approved candidate's authoritative build, test, analyzer, structural, or bounded manual verification and bind the observed result to the exact candidate. Use when implementation or review needs independently reproducible execution results. Do not change source, fix failures, judge test ad

• write-readme

  Orient readers with evidence-based README files in .NET repositories. Use for a repository entry point, package consumer guide beside a csproj, or directory map that must explain first use, capabilities, responsibilities, or navigation, including orientation requested by another project-development

Similar plugins