← all publishers

Lnscc

@lnscc source repo

Report this profile Claim this profile

• 5 skills
• 0 followers
• 20 hours ago last updated

1. ▌
   Keep It Simple · lnscc bundle

   Keep created or edited code, documentation, skills, plans, configuration, messages, and other artifacts simple, efficient, and minimal. Use the smallest clear and complete result without sacrificing correctness, safety, requirements, or repository conventions.
   0 installs
2. ▌
   Project Overview · lnscc bundle

   Plan or document a project in one repository-local Markdown overview covering purpose, architecture, modules, key libraries, flows, configuration, and development workflows. Use before implementation to design a project, or afterward to refresh its living documentation against the codebase. Do not use for task-level implementation plans or production code changes.
   0 installs
3. ▌
   Engineering Ticket · lnscc

   Create or refine one repository-local YAML ticket for a proposed code change. Use to capture requirements, scope, constraints, acceptance criteria, and open questions before impact analysis or planning. Do not analyze implementation impact, plan work, or modify production code.
   0 installs
4. ▌
   Implementation Plan · lnscc

   Turn an existing YAML ticket and its impact mapping into the smallest executable implementation plan. Use to define ordered subtasks, dependencies, acceptance criteria, and verification before coding. Do not create requirements, redo impact analysis, or modify production code.
   0 installs
5. ▌
   Change Impact Analysis · lnscc bundle

   Analyze an existing YAML engineering ticket against its codebase and return an evidence-backed impact mapping. Use before planning or coding to identify affected code, interfaces, data, tests, risks, and open decisions. Do not create tickets, plans, or production changes.
   0 installs